In order for projects to use the namespace property of Targets
in a backwards compatible way (To support rolling upgrades),
a Target may now belong to more than a single namespace (i.e.
'namespace1' and None). This way, if the server is upgraded first,
the version that introduces namespaces to a project will place
the server RPC methods in ['some_namespace', None]. Pre-upgrade
agents will send messages in the null namespace while post-upgrade
agents will send messages in 'some_namespace', and both will be
accepted.
Reviewed: https:/ /review. openstack. org/163673 /git.openstack. org/cgit/ openstack/ oslo.messaging/ commit/ ?id=3be95adcebf ef6e862eda2827a 216048b4e9007a
Committed: https:/
Submitter: Jenkins
Branch: master
commit 3be95adcebfef6e 862eda2827a2160 48b4e9007a
Author: Assaf Muller <email address hidden>
Date: Wed Mar 11 21:39:54 2015 -0400
Add support for multiple namespaces in Targets
In order for projects to use the namespace property of Targets
in a backwards compatible way (To support rolling upgrades),
a Target may now belong to more than a single namespace (i.e.
'namespace1' and None). This way, if the server is upgraded first,
the version that introduces namespaces to a project will place
the server RPC methods in ['some_namespace', None]. Pre-upgrade
agents will send messages in the null namespace while post-upgrade
agents will send messages in 'some_namespace', and both will be
accepted.
Change-Id: I713fe9228111c3 6aa3f7fb95cbd59 c99100e8c96
Closes-Bug: #1430984