Move role deployment steps into puppet/post.yaml
authorSteven Hardy <shardy@redhat.com>
Mon, 5 Sep 2016 17:40:35 +0000 (18:40 +0100)
committerSteven Hardy <shardy@redhat.com>
Fri, 9 Sep 2016 10:04:12 +0000 (11:04 +0100)
commit54a0286106e716250231dbd80e467dbe85a160a5
tree925ab43765e7740bf5e6b0508658a410558b061d
parent56486057c7c242745a4d44df5a03947ef49b49e7
Move role deployment steps into puppet/post.yaml

To enable steps to be aligned between roles, we need to define
dependencies between the steps, which is only possible if we
move the steps out of distinct nested stacks so we can use
depends_on to serialized the steps for all roles.

Note that we may be able to further refactor later to remove the
per-role -config.yaml nested stacks as well.

Change-Id: Ia2ea559e8eeb64763908f75705e3728ee90b5744
Partially-Implements: blueprint custom-roles
12 files changed:
overcloud-resource-registry-puppet.yaml
overcloud.yaml
puppet/blockstorage-config.yaml [new file with mode: 0644]
puppet/ceph-storage-post.yaml [deleted file]
puppet/cephstorage-config.yaml [new file with mode: 0644]
puppet/cinder-storage-post.yaml [deleted file]
puppet/compute-config.yaml [new file with mode: 0644]
puppet/compute-post.yaml [deleted file]
puppet/controller-post.yaml [deleted file]
puppet/objectstorage-config.yaml [new file with mode: 0644]
puppet/post.yaml [new file with mode: 0644]
puppet/swift-storage-post.yaml [deleted file]