Compute: Exec puppet after all configuration
authorDan Prince <dprince@redhat.com>
Thu, 19 Feb 2015 23:54:24 +0000 (15:54 -0800)
committerDan Prince <dprince@redhat.com>
Tue, 24 Feb 2015 01:45:01 +0000 (20:45 -0500)
commitb11ac7e6b67c08eb7407872ece519f2675151483
treee9671adf67ea1f6fa326400a435a3ad3b977b47e
parent62ab434139c4576afe84b7b0b08374261fc79563
Compute: Exec puppet after all configuration

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