yahoo-eng-team team mailing list archive

[Chris Friesen <chris.friesen@xxxxxxxxxxxxx>]

Just to clarify something, availability zones don't "have" host
aggregates.  Rather, some host aggregates *are also* availability zones,
but a given host can only be in one availability zone.

I went and looked at the code, and the way it is currently written I
think it is actually okay to have multiple host aggregates specifying
the same availability zone.

The logic in the AvailabilityZoneFilter is basically to loop over all
host aggregates for the host in question, and if one of them has an
availability zone (there should be only one) then the filter will check
it against the availability zone specified by the user.

As such, I'm going to close this bug.

** Changed in: nova
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1213224

Title:
  nova allows multiple aggregates with same zone name

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Currently (on grizzly), nova will let you specify multiple aggregates
  with the same zone name.

  This seems like a mismatch since the end-user can only specify an
  availability zone when creating an instance, and there could be
  multiple aggregates (with different hosts) mapping to that zone.

  On aggregate creation, nova should ensure that the availability zone
  name (if specified) is not a duplicate of an existing availability
  zone name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1213224/+subscriptions