ObjectStore: Exec puppet after all configuration
authorDan Prince <dprince@redhat.com>
Fri, 20 Feb 2015 00:31:38 +0000 (16:31 -0800)
committerDan Prince <dprince@redhat.com>
Tue, 24 Feb 2015 01:45:03 +0000 (20:45 -0500)
commit66aaf72d35fc7c9be5d4fc7605f8ad6d7b5c520e
treefaf2f1fd7b83d037a9e825d30ddb58486903861a
parentb11ac7e6b67c08eb7407872ece519f2675151483
ObjectStore: Exec puppet after all configuration

This patch adds a new ObjectStoreNodesPostDeployment resource
which can be used along with the environment file to
specify a nested stack which is guaranteed to execute
after all the ObjectStore 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: I778b87a17d5e6824233fdf9957c76549c36b3f78
overcloud-resource-registry-puppet.yaml
overcloud-resource-registry.yaml
overcloud-without-mergepy.yaml
puppet/swift-storage-post.yaml [new file with mode: 0644]
puppet/swift-storage-puppet.yaml
swift-storage-post.yaml [new file with mode: 0644]