03697234fd
In I12a02f636f31985bc1b71bff5b744d346286a95f cell_v2 discovery was
originally moved from the nova-api container to the
nova-compute|nova-ironic containers in order to run cell
discovery during a scale up where the controllers are omitted
(e.g to exclude the controllers from a maintenance window).
This requires api database credentials on the compute node, which is
forbidden, so it must move back to a nova-api host as a pre-requisite
for removing these credentials in a follow-up patch.
Scale-up while omitting the controllers will no longer work out of the
box. Either a manual cell_v2 discovery can be run after scale up, or an
additional node can be deployed using the NovaManager tripleo role.
Related-bug: #1786961
Related-bug: #1871482
Change-Id: I47b95ad46e2d4e5b1f370a2f840826e87da2d703
(cherry picked from commit 629485dde5)
14 lines
702 B
YAML
14 lines
702 B
YAML
---
|
|
issues:
|
|
- |
|
|
Cell_v2 discovery has been moved from the nova-compute|nova-ironic
|
|
containers as this requires nova api database credentials which must
|
|
not be configured for the nova-compute service.
|
|
As a result scale-up deployments which explicitly omit the Controller
|
|
nodes will need to make alternative arrangements to run cell_v2 discovery.
|
|
Either the nova-manage command can be run manually after scale-up, or
|
|
an additional helper node using the NovaManage role can be deployed that
|
|
will be used for this task instead of a Controller node. See Bug:
|
|
`1786961 <https://launchpad.net/bugs/1786961>`_ and Bug:
|
|
`1871482 <https://launchpad.net/bugs/1871482>`_.
|