Oliver Walsh e0e885b8ca Move cellv2 discovery from control plane services to compute services ... If compute nodes are deployed without deploying/updating the controllers then the computes will not have cellv2 mappings as this is run in the controller deploy steps (nova-api). This can happen if the controller nodes are blacklisted during a compute scale out. It's also likely to be an issue going forward if the deployment is staged (e.g split control plane). This change moves the cell_v2 discovery logic to the nova-compute/nova-ironic deploy step. Closes-bug: 1786961 Change-Id: I12a02f636f31985bc1b71bff5b744d346286a95f		2018-12-20 11:23:06 +05:30
..
tests	Improve nova statedir ownership logic	2018-07-09 17:07:30 +01:00
__init__.py	Improve nova statedir ownership logic	2018-07-09 17:07:30 +01:00
nova_cell_v2_discover_host.py	Move cellv2 discovery from control plane services to compute services	2018-12-20 11:23:06 +05:30
nova_statedir_ownership.py	Move cellv2 discovery from control plane services to compute services	2018-12-20 11:23:06 +05:30
nova_wait_for_placement_service.py	nova_compute fails to start in tls-everywhere configuration	2018-12-03 17:07:28 +01:00
pyshim.sh	Correct file modes for rpmlint failures	2018-12-14 13:21:28 -07:00