yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #65317
[Bug 1474467] Re: default_schedule_zone should be list
This wishlist bug has been open a year without any activity.
I'm going to move it to "Opinion", which is an easily-obtainable queue of older requests that have come on.
This bug can be reopened (set back to "New") if someone decides to work on this.
** Changed in: nova
Status: Confirmed => Opinion
--
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/1474467
Title:
default_schedule_zone should be list
Status in OpenStack Compute (nova):
Opinion
Bug description:
I'd like to re-open or re-state the issue reported in
https://bugs.launchpad.net/nova/+bug/1037371 .
Let us say that I have 3 availability zones: nova, az1, az2. I do not
care if I land in nova or az1 if no AZ is specified on boot but az2 is
"special" and I do *not* want to land there by default. The only way
around this that I can think of would be to disable the hypervisors in
the az2 AZ and boot to them manually. However, if I disable the nodes
in AZ2 I cannot simply boot to az2 and let the scheduler make the
appropriate choice about where to schedule the instance.
It seems like it would make sense for default_schedule_zone to be a
list option or since that might be a pain to keep track of... for
there to be a sort of "inverse" option like excluded_schedule_zones.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1474467/+subscriptions
References