yahoo-eng-team team mailing list archive

[Russell Bryant <1037371@xxxxxxxxxxxxxxxxxx>]

I just came back to this bug and looked at the code and this option
actually defaults to None.  That means it should behave just like you
want it to by default.  Just don't set this option.

** 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/1037371

Title:
  default_schedule_zone is not intelligent

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  When launch a instance, use can specific a availability_zone. If user
  does't specific availability_zone, nova-api will set it to
  conf.default_schedule_zone.

  But think about this :
    I have three availability_zone: nova, az1, az2

  When user does't specific availability_zone, the instance will always in zone - nova. But this will make zone nova busy.
  I see availability_zone_filter will pass all the host if user do not specific any availability_zone (#last line):
  --------------------------------------------
      def host_passes(self, host_state, filter_properties):
          spec = filter_properties.get('request_spec', {})
          props = spec.get('instance_properties', {})
          availability_zone = props.get('availability_zone')

          if availability_zone:
              return availability_zone == host_state.service['availability_zone']
          return True
  -------------------------------------------------

  Maybe nova-api don't need to set availability_zone to default_schedule_zone, Just that it empty.
  In this way nova-scheduler can use nova, az1, az2 to launch new instance.

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