Disable puppet on upgrade for roles not upgrading
authorSteven Hardy <shardy@redhat.com>
Thu, 2 Feb 2017 12:03:03 +0000 (12:03 +0000)
committerSteven Hardy <shardy@redhat.com>
Fri, 3 Feb 2017 11:43:47 +0000 (11:43 +0000)
commit87af02d67336ff26c47f67c40df23dad9e66b7fd
tree58b1a484dbda146d8bd1e24def5c90276089e311
parentec24ed7dd82fd4c1553085719e369b545c4beedd
Disable puppet on upgrade for roles not upgrading

Where the role has disabled upgrades, we need to skip both the ansible and
puppet steps.  To do this we refactor the post.j2.yaml so that it can be
included in the upgrade template with an adjusted list of roles.

Note this requires https://review.openstack.org/#/c/425220/ - this
change will be required for local testing of this patch
(run mistral-db-mange populate after updating tripleo-common
and restart the mistral services, or update your repos and re-run
openstack undercloud install).

Partially-Implements: blueprint overcloud-upgrades-per-service
Change-Id: Ie7d0fa6fef3528bd93e6cde076b964ea8de3185a
environments/major-upgrade-all-in-one.yaml
environments/major-upgrade-composable-steps.yaml
overcloud-resource-registry-puppet.j2.yaml
overcloud.j2.yaml
puppet/major_upgrade_steps.j2.yaml
puppet/post-upgrade.j2.yaml [new file with mode: 0644]
puppet/post.j2.yaml
puppet/puppet-steps.j2 [new file with mode: 0644]