Expose enable_new_services=True/False as a dedicated config option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Cloud Controller Charm |
Fix Released
|
Wishlist
|
Andre Ruiz |
Bug Description
While enable_
When a deployment rely on host aggregates to distinguish the type of nova-compute hosts (KVM vs LXD or Generic vs SR-IOV), it's not convenient that the new host will be enabled out of the box with the default AZ (nova).
By setting enable_
See the example output below.
$ openstack compute service list --service nova-compute --long
+----+-
| ID | Binary | Host | Zone | Status | State | Updated At | Disabled Reason |
+----+-
| 31 | nova-compute | nodz001 | myaz-foo-a | enabled | up | 2018-03-
| 34 | nova-compute | nodp004 | myaz-foo-a | enabled | up | 2018-03-
| 40 | nova-compute | nodp005 | myaz-foo-b | enabled | up | 2018-03-
| 43 | nova-compute | nodp001 | myaz-foo-a | enabled | up | 2018-03-
| 46 | nova-compute | nodp002 | myaz-foo-b | enabled | up | 2018-03-
| 52 | nova-compute | nodz003 | nova | disabled | up | 2018-03-
| 55 | nova-compute | nodp006 | nova | disabled | up | 2018-03-
| 58 | nova-compute | nodz002 | myaz-foo-b | enabled | up | 2018-03-
| 61 | nova-compute | nodp003 | nova | disabled | up | 2018-03-
+----+-
-----+-
Changed in charm-nova-cloud-controller: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Changed in charm-nova-cloud-controller: | |
assignee: | nobody → Andre Ruiz (andre-ruiz) |
Changed in charm-nova-cloud-controller: | |
milestone: | none → 19.04 |
Changed in charm-nova-cloud-controller: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/637853
Review: https:/