Martin Schuppert 58b65c1da8 Move nova cell v2 discovery to deploy_steps_tasks ... Recent changes for e.g edge scenarios caused intended move of discovery from controller to bootstrap compute node. The task is triggered by deploy-identifier to make sure it gets run on any deploy,scale, ... run. If deploy run is triggered with --skip-deploy-identifier flag, discovery will not be triggered at and as result causing failures in previously supported scenarios. This change moves the host discovery task to be an ansible deploy_steps_tasks that it gets triggered even if --skip-deploy-identifier is used, or the compute bootstrap node is blacklisted. Closes-Bug: #1831711 Conflicts: deployment/nova/nova-compute-container-puppet.yaml docker/services/nova-compute-common.yaml docker/services/nova-ironic.yaml docker_config_scripts/nova_cell_v2_discover_hosts.py Change-Id: I4bd8489e4f79e3e1bfe9338ed3043241dd605dcb (cherry picked from commit f8779e5023) (cherry picked from commit b82417126b)		2019-07-09 11:24:01 +02:00
..
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_statedir_ownership.py	Move cellv2 discovery from control plane services to compute services	2019-03-05 10:59:20 +05:30
nova_wait_for_compute_service.py	Avoid concurrent nova cell_v2 discovery instances	2019-04-25 11:31:20 +02:00
nova_wait_for_placement_service.py	nova_compute fails to start in tls-everywhere configuration	2018-12-04 11:35:39 +01:00