Update puppet post config to enable stepped deployments
authorGiulio Fidente <gfidente@redhat.com>
Wed, 18 Mar 2015 16:54:33 +0000 (12:54 -0400)
committerGiulio Fidente <gfidente@redhat.com>
Wed, 18 Mar 2015 16:54:33 +0000 (12:54 -0400)
commitccbdc85948117b1bb8323154846ec27a533004fb
tree0acb0bebd80ebb83b714507340c48725e0ee9b58
parent5e7928431e0ba0afd91ef924d43ca5fb28b345fa
Update puppet post config to enable stepped deployments

The upcoming heat hook/breakpoint features will enable stepped deployments
via setting stop points via the resource_registry.

For this to work, we need hard dependencies between each step of the
puppet deployments, because the current "soft" dependencies caused by the
name property only influences the hook script application ordering, not
the graph traversed by heat during deployment.

Since removing the name: puppet_n completely removes some useful self-
documenting context, move this to a resource naming convention, which
should also be useful for heat hooks/breakpoints, as they are expected
to support globbed specification of each step.

Related heat patch (not yet landed, but this is not dependent on it):

https://review.openstack.org/#/c/146123/

Change-Id: I05b02a46d4e80c08a308d033c33d4901c8f6c94e
puppet/ceph-storage-post-puppet.yaml
puppet/cinder-storage-post.yaml
puppet/controller-post-puppet.yaml
puppet/swift-storage-post.yaml