yahoo-eng-team team mailing list archive

[Yang Yu <yuyangbj@xxxxxxxxxx>]

Basing on the current design, we should keep the AZ check in scheduler
layer because current OpenStack could force the host to boot. For
example,

nova boot --availability_zone foobar:host1

The VM will be created on compute host1 even though the foobar is not
existing. So if we add the AZ check in api layer, it will break current
design. So mark this bug to invalid.

** Changed in: nova
       Status: New => 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/1185367

Title:
  AZ should be validated durign instance create at the api layer

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  Currently the compute API layer does not do any validation of the
  availability zone, so a request like:

  nova boot --availability_zone foobar

  will be accepted, sent to the scheduler, and the instance will go to
  error.

  There is already code in compute/api.py  which processes  the
  availability_zone  value

  def _handle_availability_zone(availability_zone)
  ...

  
  So it seems like there should be some basic validation added to check that the zone exists and is available

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