Fix AvailabilityZone check for hosts in multiple aggregates
Check for multiple AZ was distinct when adding an host to an aggregate
and when updating an aggregate (or its metadata), which was leading to
possible corner-cases where logics were different.
This patch proposes a single way for checking for both API methods and
also adds an extra control on the possibility to have an aggregate with
its metadata AZ set to the configuration default value (eg. 'nova') and
where it was possible to subsequently have one host in two disctinct AZs
Fixed that scenerio as it is a gap, Nova as of now preventing to have
one host in two distinct AZs.
Reviewed: https:/ /review. openstack. org/85961 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=0ad5a64dc9a c4b1cfb8038f917 1b6385fdf07f28
Committed: https:/
Submitter: Jenkins
Branch: master
commit 0ad5a64dc9ac4b1 cfb8038f9171b63 85fdf07f28
Author: Sylvain Bauza <email address hidden>
Date: Tue Apr 8 11:00:40 2014 +0200
Fix AvailabilityZone check for hosts in multiple aggregates
Check for multiple AZ was distinct when adding an host to an aggregate
and when updating an aggregate (or its metadata), which was leading to
possible corner-cases where logics were different.
This patch proposes a single way for checking for both API methods and
also adds an extra control on the possibility to have an aggregate with
its metadata AZ set to the configuration default value (eg. 'nova') and
where it was possible to subsequently have one host in two disctinct AZs
Fixed that scenerio as it is a gap, Nova as of now preventing to have
one host in two distinct AZs.
Change-Id: Ida6aa507f34f36 a436adaafe1f760 9963c59a9bc
Partial-Bug: #1277230