14793d701d
Based on [1], this patch implements changes to the playbook which executes the neutron deployment in a play per host group, serialised to ensure that: 1. The services are changed in the right order. 2. The API services remain available at all times during an upgrade (except when doing a db contract). 3. If services are sharing a host/container then the role execution will not execute twice on the same host. [1] https://docs.openstack.org/developer/neutron/devref/upgrade.html Depends-On: I368b51ef37763f4163ead591d6743c4d56962ef9 Depends-On: I7dfef45e1ed8a8dfa464f1b3d20c90ae3348ce2e Change-Id: Ib9067042066e9b5b2cd7418ea7f7f96225302852
8 lines
310 B
YAML
8 lines
310 B
YAML
---
|
|
features:
|
|
- |
|
|
The ``os-neutron-install.yml`` playbook will now execute a rolling
|
|
upgrade of neutron including database migrations (both expand and
|
|
contract) as per the procedure described in the
|
|
`neutron documentation <https://docs.openstack.org/developer/neutron/devref/upgrade.html>`_.
|