7fc1497ebe
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
10 lines
323 B
YAML
10 lines
323 B
YAML
---
|
|
features:
|
|
- The ``os_nova`` role now provides for doing
|
|
online data migrations once the db sync has
|
|
been completed. The data migrations will not
|
|
be executed until the boolean variable
|
|
``nova_all_software_updated`` is true. This
|
|
variable will need to be set by the playbook
|
|
consuming the role.
|