Updates simple scheduler to allow strict availability_zone scheduling

This update adds strict availability_zone scheduling of new instances when
an availabity_zone option is not present in the creation call.  This patch
does not change the expected default behavior.

Previous behavior was to default the zone to None and only update the zone
in the scheduler if an availability_zone was supplied.  This incorrectly
allowed the scheduler to place new instances created without an
availability_zone onto compute nodes where the availability_zone had been
changed to something other than the default of 'nova'.

Setting default_schedule_zone to 'nova' will prevent new instance scheduling
into availability_zones other than the default 'nova' zone.  This change
defaults the zone to None but allows the user to override this with the
default_schedule_flag.

In practice, if you have 2 availability_zones (nova, megazone) you can
configure default_schedule_zone on the API node to 'nova' and any instances
created will be created into the 'nova' availability_zone if one was not
supplied.  Instances created with an availability_zone will be created as
normal into the availability_zone supplied.

Change-Id: Id23bac8448ea7ce6a1e1227d046c921328dbfe33

0 files changed, 0 insertions, 0 deletions