diff options
author | Steven Hardy <shardy@redhat.com> | 2017-07-21 11:43:25 +0100 |
---|---|---|
committer | Emilien Macchi <emilien@redhat.com> | 2017-08-12 10:40:48 +0000 |
commit | 1801565a75018fea1d6c8fd30543c9b238167652 (patch) | |
tree | 18fc7a95a821ea49d6f7f61ac530dabf096acbd0 /sample-env-generator | |
parent | 46279be9cb77ec9cf6e53e77c239a51efda06d80 (diff) |
Add support for update_tasks
These work the same way as upgrade_tasks *but* they use a step variable
instead of tags, so we can iterate over a count/sequence which isn't
possibly via a wrapper playbook with tags (we may want to align upgrade
tasks with the same approach if this works out well).
Note the tasks can be run via ansible-playbook on the undercloud, like:
openstack overcloud config download --config-dir tmpconfig
cd tmpconfig/tripleo-HCrDA6-config
ansible-playbook -b -i /usr/bin/tripleo-ansible-inventory update_steps_playbook.yaml --limit controller
The above will do a rolling update for the Controller role (note the inconsistent
capitalization, we probably need to fix the group naming in tripleo-ansible-inventory)
because we specify serial: 1 in the playbook.
You can also trigger an update explicitly on one node like this, which is useful for debugging:
ansible-playbook -vvv -b -i /usr/bin/tripleo-ansible-inventory update_steps_playbook.yaml --limit overcloud-controller-0
Change-Id: I20bb3e26ab9d9cadf1a31fd304de8a014a901aa9
Diffstat (limited to 'sample-env-generator')
0 files changed, 0 insertions, 0 deletions