Reviewed: https://review.openstack.org/289193 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=fc771f1616a13259e4d8d86d6f414eb135c61a9d Submitter: Jenkins Branch: master
commit fc771f1616a13259e4d8d86d6f414eb135c61a9d Author: Yingxin <[email protected]> Date: Fri Feb 26 02:34:16 2016 +0000 Reject empty-named AZ in aggregate metadata The empty-named AZ is meaningless and confusing. It isn't the default AZ. It is confusing when we list AZ using `nova availability-zone-list`. And, nova scheduler cannot distinguish between the empty-named AZ and the default AZ. See the detailed explanation of bug 1523450. Change-Id: I8e03880062d81392c3701d09bf37cf35abe09f8d Closes-Bug: #1523450 ** Changed in: nova Status: In Progress => Fix Released -- 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/1523450 Title: Empty-named AZ is accepted using aggregate-set-metadata Status in OpenStack Compute (nova): Fix Released Bug description: An empty-named AZ can be set using the following command if there exists an aggregate 'foo': $nova aggregate-set-metadata foo availability_zone= +----+------+-------------------+---------+----------------------+ | Id | Name | Availability Zone | Hosts | Metadata | +----+------+-------------------+---------+----------------------+ | 55 | foo | | 'node2' | 'availability_zone=' | +----+------+-------------------+---------+----------------------+ This empty-named AZ is meaningless and confusing, because it ISN'T the default AZ. For example if we list AZ there will be an empty entry: $nova availability-zone-list +-----------------------+----------------------------------------+ | Name | Status | +-----------------------+----------------------------------------+ | internal | available | | |- node1 | | | | |- nova-conductor | enabled :-) 2015-12-07T08:15:49.000000 | | | |- nova-consoleauth | enabled :-) 2015-12-07T08:15:50.000000 | | | |- nova-scheduler | enabled :-) 2015-12-07T08:15:50.000000 | | | |- nova-cert | enabled :-) 2015-12-07T08:15:51.000000 | | | available | | |- node2 | | | | |- nova-compute | enabled :-) 2015-12-07T08:15:49.000000 | | nova | available | | |- node3 | | | | |- nova-compute | enabled :-) 2015-12-07T08:15:50.000000 | +-----------------------+----------------------------------------+ However, nova scheduler CANNOT distinguish between this empty-named AZ and the default AZ, for example: $nova boot --flavor 42 --image <image> --availability-zone "" test The scheduler will treat "" as default AZ, the 'test' instance will be booted in either "" or the default "nova" AZ. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1523450/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
