2e182bffee
This adds a new config/deployment per role that will come after any post deploy steps. It drives the same ansible config as the upgrade_tasks but instead collects the post_upgrade_tasks for any service in the given role. The workflow is upgrade_tasks, then post deploy steps (either puppet/ or docker/ depending on the env) and then the post_upgrade_tasks added here. This is added to the pacemaker/cinder-volume.yaml service for now see the bug below for more info Change-Id: Iced34fecf02ebddc91df9302de54d2f4c2cab680 Closes-Bug: 1706951
13 lines
535 B
YAML
13 lines
535 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
This adds post_upgrade_tasks, ansible tasks that can be added to any
|
|
service manifest (currently, pacemaker/cinder-volume for bug 1706951).
|
|
|
|
These are similar to the existing upgrade_tasks in their format, however
|
|
they will be executed *after* the docker/puppet config. So the order is
|
|
upgrade_tasks, deployment steps (docker/puppet), then post_upgrade_tasks.
|
|
|
|
Also like the upgrade_tasks these are serialised and you can use 'tags'
|
|
with 'step0' to 'step6' (more can be added if needed).
|