Update version aliases for rpc version control

Now that Havana has been branched, add aliases for the rpc version
implemented by Havana.  These aliases can be used in the configuration
options for doing outbound rpc version control.

This is one of the items that should be done after every release, and
has been added to the new release checklist wiki page:

    https://wiki.openstack.org/wiki/Nova/ReleaseChecklist

DocImpact - 'havana' is now a valid value to provide to all of the
options in the [upgrade_levels] section of nova.conf.

Change-Id: Ifa0b3dcc00843ad3f045a450ceb0f47f0b843f98
This commit is contained in:
Russell Bryant
2013-10-14 14:41:28 -04:00
parent 158c84733b
commit 730283ab6e

View File

@@ -71,6 +71,11 @@ class SchedulerAPI(rpcclient.RpcProxy):
2.8 - Deprecate prep_resize() -- JUST KIDDING. It is still used
by the compute manager for retries.
2.9 - Added the legacy_bdm_in_spec parameter to run_instance()
... Havana supports message version 2.9. So, any changes to existing
methods in 2.x after that point should be done such that they can
handle the version_cap being set to 2.9.
... - Deprecated live_migration() call, moved to conductor
'''
@@ -86,6 +91,7 @@ class SchedulerAPI(rpcclient.RpcProxy):
VERSION_ALIASES = {
'grizzly': '2.6',
'havana': '2.9',
}
def __init__(self):