cb62372a31
According to nova rolling upgrade process [1], online_data_migrations should run once all the services are running the latest version of the code and were restarted. With that, we should move online migrations after handlers being flushed, when all services are restarted. At the same time, nova-status upgrade check must run before services are restarted to the new version, as service restart might lead to service breakage if upgrade check fails [2]. It makes no sense to run upgrade check when upgrade is fully finished. [1] https://docs.openstack.org/nova/latest/admin/upgrades.html#rolling-upgrade-process [2] https://docs.openstack.org/nova/latest/cli/nova-status.html#upgrade Change-Id: Ic681f73a09bb0ac280c227f85c6e79b31fd3429a |
||
---|---|---|
defaults | ||
doc | ||
examples | ||
files | ||
handlers | ||
meta | ||
releasenotes | ||
tasks | ||
templates | ||
tests | ||
vars | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
CONTRIBUTING.rst | ||
LICENSE | ||
README.rst | ||
Vagrantfile | ||
bindep.txt | ||
manual-test.rc | ||
run_tests.sh | ||
tox.ini |
README.rst
Team and repository tags
OpenStack-Ansible nova
Ansible role that installs and configures OpenStack nova and all of its corresponding services.
- This role will install the following:
-
- nova-api
- nova-conductor
- nova-scheduler
- nova-console
- nova-compute
Documentation for the project can be found at: https://docs.openstack.org/openstack-ansible-os_nova/latest/
Release notes for the project can be found at: https://docs.openstack.org/releasenotes/openstack-ansible-os_nova/
The project source code repository is located at: https://opendev.org/openstack/openstack-ansible-os_nova/
The project home is at: https://launchpad.net/openstack-ansible
The project bug tracker is located at: https://bugs.launchpad.net/openstack-ansible