c032792bbb
While there are some nova-manage commands to take an existing deployment and migrate all of its hosts into a new cellsv2 environment there was no way to add more hosts to a cell. This command can be run at any time after the initial migration and will map any hosts in a cell that have not been seen before. Nothing else changes about adding hosts to a deployment. Configure them to use a nova database and start them up and they'll register themselves with that database. This new command simply lets the API know how to route requests to those hosts. Until this is done instances can not be booted on those hosts. Partially-Implements: bp cells-scheduling-interaction Change-Id: I8c044e5b480edddead28d8c3527d003da566ed1e
26 lines
1.5 KiB
YAML
26 lines
1.5 KiB
YAML
---
|
|
features:
|
|
- A new nova-manage command has been added to discover any new hosts that are
|
|
added to a cell. If a deployment has migrated to cellsv2 using either the
|
|
simple_cell_setup or the map_cell0/map_cell_and_hosts/map_instances combo
|
|
then anytime a new host is added to a cell this new
|
|
"nova-manage cell_v2 discover_hosts" needs to be run before instances can
|
|
be booted on that host. If multiple hosts are added at one time the command
|
|
only needs to be run one time to discover all of them.
|
|
|
|
Please note that adding a host to a cell and not running this command could
|
|
lead to build failures/reschedules if that host is selected by the
|
|
scheduler. The discover_hosts command is necessary to route requests to the
|
|
host but is not necessary in order for the scheduler to be aware of the
|
|
host. In order to avoid that it is advised that new compute hosts are
|
|
disabled until the discover command has been run.
|
|
issues:
|
|
- If a deployer has updated their deployment to using cellsv2 using either
|
|
the simple_cell_setup or the map_cell0/map_cell_and_hosts/map_instances
|
|
combo and they add a new host into the cell it may cause build failures
|
|
or reschedules until they run the "nova-manage cell_v2 discover_hosts"
|
|
command. This is because the scheduler will quickly become aware of the
|
|
host but nova-api will not know how to route the request to that host until
|
|
it has been "discovered". In order to avoid that it is advised that
|
|
new computes are disabled until the discover command has been run.
|