yahoo-eng-team team mailing list archive

[Phil Day <1185367@xxxxxxxxxxxxxxxxxx>]

Marking this back to New because I simply don't agree with the above
analysis.

Personally I doubt if the intention of the forcehost capability was to
allow an invalid AZ name by design,  - but if there really is a need to
be able to specify an invalid AZ name when forcing to a particular host
(a privileged operation) then it would be possible to make the API
validation skip the check for a valid AZ if the name contains a ":"

Not a reason to reject making a significant improvement to the common
use case.

** Changed in: nova
       Status: Invalid => New

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

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