openstack/tripleo-heat-templates
Code Issues Proposed changes

Tag step plays

Browse Source 
This adds a tag step[1-5] to each of the plays within the jinja2 loop to
create our 5 deployment steps. Using these tags, it's possible to run
these plays individually if desired.

Change-Id: Ic705afbf174b4597d98c2b83041ff88dd8d6664c
This commit is contained in:
James Slagle 2018-08-31 16:59:03 -04:00
parent 300c366701
commit bf6efb06c7
2 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
common/deploy-steps.j2
View File

@ -526,6 +526,7 @@ outputs:
tags:
- external
- external_deploy_steps
- step{{step}}
- hosts: {{primary_role_name}}:DEPLOY_TARGET_HOST
name: Overcloud deploy step tasks for {{step}}
@ -551,6 +552,7 @@ outputs:
tags:
- overcloud
- deploy_steps
- step{{step}}
- hosts: {{primary_role_name}}:DEPLOY_TARGET_HOST
name: Overcloud common deploy step tasks {{step}}
@ -565,6 +567,7 @@ outputs:
tags:
- overcloud
- deploy_steps
- step{{step}}
{%- endfor %}
- hosts: {{primary_role_name}}:DEPLOY_TARGET_HOST

5
releasenotes/notes/tag-step-plays-b1b1ea7584f1665d.yaml Normal file
View File

@ -0,0 +1,5 @@
---
other:
- The step plays in deploy-steps.j2 (which generates the
deploy_steps_tasks.yaml playbook) are now tagged with step[1-5] so that
they can run individually if needed.