[Yahoo-eng-team] [Bug 1185367] Re: AZ should be validated durign instance create at the api layer
** Changed in: nova Status: Fix Committed = Fix Released ** Changed in: nova Milestone: None = havana-3 -- 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): Fix Released 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1185367] Re: AZ should be validated durign instance create at the api layer
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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1185367] Re: AZ should be validated durign instance create at the api layer
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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
