This is very low priority bug.
You can only see the view above if you are an admin, so 'internal' is
only a key word in those cases.
The use can only use this to make their own host fail to boot. While it
might be nicer to validate their AZ up front, I'm not entirely convinced
this is any different than them trying to push to the 'bogus' az.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Status: Opinion => Confirmed
** Changed in: nova
Importance: Undecided => Low
** Changed in: nova
Importance: Low => Wishlist
** Changed in: nova
Status: Confirmed => Opinion
--
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/1523459
Title:
Instance can be booted into the "internal" availability zone
Status in OpenStack Compute (nova):
Opinion
Bug description:
Currently, only the nova-compute service has its own availability zone.
Services such as nova-scheduler, nova-network, and nova-conductor appear in
the AZ named "internal". (ref:
http://docs.openstack.org/openstack-ops/content/scaling.html) For example:
$ nova availability-zone-list
+-----------------------+----------------------------------------+
| Name | Status |
+-----------------------+----------------------------------------+
| internal | available |
| |- node1 | |
| | |- nova-conductor | enabled :-) 2015-12-07T11:38:09.000000 |
| | |- nova-consoleauth | enabled :-) 2015-12-07T11:38:05.000000 |
| | |- nova-scheduler | enabled :-) 2015-12-07T11:38:12.000000 |
| | |- nova-cert | enabled :-) 2015-12-07T11:38:07.000000 |
| nova | available |
| |- node2 | |
| | |- nova-compute | enabled :-) 2015-12-07T11:38:12.000000 |
| |- node3 | |
| | |- nova-compute | enabled :-) 2015-12-07T11:38:12.000000 |
+-----------------------+----------------------------------------+
However, we can schedule an instance to the "internal" AZ using following
command:
$ nova boot --flavor 42 --image <image> --availability-zone "internal" test
Succeed with no error message!
But this "test" instance will be in ERROR status because there is no compute
node in the "internal" AZ.
$ nova list
+--------------------------------------+------+--------+------------+-------------+----------+
| ID | Name | Status | Task State | Power
State | Networks |
+--------------------------------------+------+--------+------------+-------------+----------+
| eca73033-15cf-402a-b39a-a91e497e3e07 | test | ERROR | - | NOSTATE
| |
+--------------------------------------+------+--------+------------+-------------+----------+
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1523459/+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
