Oliver Walsh d8e4ee655e Avoid concurrent nova cell_v2 discovery instances ... The nova_cell_v2_discover_hosts.py was moved to run on compute nodes instead of controllers to allow adding computes without touching controllers and in case multiple stacks are used to manage compute nodes. In case the nova-manage command, run by nova_cell_v2_discover_hosts.py, gets triggered at the same time on compute nodes races. With this change if this is _not_ an additional cell: * in docker_config step4, on every compute, we start the nova-compute container and then start a (detach=false) container to wait for it's service to appear in the service list. * in docker_config step5, on the bootstrap node only, we run the discovery. Change-Id: I1a159a7c2ac286373df2b7c566426b37b7734961 Closes-bug: 1824445 Co-authored-by: mschuppert@redhat.com (cherry picked from commit 908e6b9810) (cherry picked from commit 8fd58b4b87) (cherry picked from commit cf6ae21fc9)		2019-04-25 11:35:17 +02:00
..
tests	Improve nova statedir ownership logic	2018-07-25 16:49:52 +02:00
__init__.py	Improve nova statedir ownership logic	2018-07-25 16:49:52 +02:00
nova_cell_v2_discover_hosts.py	Avoid concurrent nova cell_v2 discovery instances	2019-04-25 11:35:17 +02:00
nova_statedir_ownership.py	Move cellv2 discovery from control plane services to compute services	2019-03-06 11:01:33 +05:30
nova_wait_for_compute_service.py	Avoid concurrent nova cell_v2 discovery instances	2019-04-25 11:35:17 +02:00
nova_wait_for_placement_service.py	nova_compute fails to start in tls-everywhere configuration	2018-12-17 13:45:00 +00:00