Jesse Pretorius 7fc1497ebe Implement data migrations for rolling upgrades
In order to cater for artifact-based installed, and
rolling upgrades, this patch implements a set of local
facts to inform the online migrations task.

The 'nova_all_software_updated' variable will be
set by the playbook on each run to ensure that the
online migrations only happen once all venvs are
homogenous. This ensures that the playbook can be
executed in a serialised fashion and the data will
not be corrupted.

The ``upgrade_levels`` setting for ``compute`` is set
to ``auto`` to ensure that a mixed RPC version
deployment can operate properly when doing a rolling
upgrade as suggested by [1].

Additional changes are made to improve the role's
ability to be executed using serialised playbooks.

Finally, the nova-manage command references to the
config file location have been removed as they refer
to the default location.

[1] https://docs.openstack.org/developer/nova/upgrade.html
Change-Id: I08e5a7f0ce526b11aa52c35ee29c458954a5f22d
2017-07-06 06:18:21 +00:00
2017-07-03 16:00:53 +01:00
2017-07-03 16:20:59 +08:00
2017-06-21 11:58:00 +01:00
2016-09-28 10:27:39 +01:00
2016-11-25 16:15:31 +01:00
2017-03-02 11:52:00 +00:00

Team and repository tags

image

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: http://docs.openstack.org/developer/openstack-ansible-os_nova/

The project home is at: http://launchpad.net/openstack-ansible

Description
Role os_nova for OpenStack-Ansible
Readme 15 MiB
Languages
Jinja 58.9%
Python 27.9%
Shell 13.2%