BlockStore: Exec puppet after all configuration
authorDan Prince <dprince@redhat.com>
Mon, 23 Feb 2015 19:00:24 +0000 (14:00 -0500)
committerDan Prince <dprince@redhat.com>
Tue, 24 Feb 2015 01:45:03 +0000 (20:45 -0500)
commit3ced063b490cb05bf2332e85358c795e367491ce
tree63d82348a4204553744a72bfbcb11da665695647
parent66aaf72d35fc7c9be5d4fc7605f8ad6d7b5c520e
BlockStore: Exec puppet after all configuration

This patch adds a new BlockStoreNodesPostDeployment resource
which can be used along with the environment file to
specify a nested stack which is guaranteed to execute
after all the BlockStore config deployments have executed.

This is really useful for Puppet in that Heat actually
controls where puppet executes in the deployment
process and we want to ensure puppet runs after
all hiera configuration data has be deployed to
the nodes. With the previous approach some of the
data would be there, but allNodes data would not be
guaranteed to be there in time.

As os-apply-config (tripleo-image-elements) have their
ordering controlled within the elements themselves an empty stubbed
in nested stack has been added so that we don't break that
implementation.

Change-Id: I29b3574e341eecd53b2867788f415bff153cfa9f
cinder-storage-post.yaml [new file with mode: 0644]
overcloud-resource-registry-puppet.yaml
overcloud-resource-registry.yaml
overcloud-without-mergepy.yaml
puppet/cinder-storage-post.yaml [new file with mode: 0644]
puppet/cinder-storage-puppet.yaml