yahoo-eng-team team mailing list archive

[Kevin Stevens <kevin@xxxxxxxxx>]

Public bug reported:

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 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.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: scheduler

-- 
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):
  New

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 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