[Openstack-operators] Nodes and configurations management in Puppet

Mathieu Gagné mgagne at iweb.com
Fri Sep 26 18:02:08 UTC 2014

Hi Clayton,

Thanks for sharing your experience and use of Puppet with OpenStack.

I feel less alone now. :)

On 2014-09-25 1:42 PM, Clayton O'Neill wrote:
> We have a single default node definition.  We have a custom fact that
> determines the node's role based on it's hostname, then includes a
> derived class ("include role::${::role}") based off of that
> information.  Since we're using something very similar to Craig Dunn's
> roles/profiles pattern, and we store all the configuration in hiera, I
> feel like we're getting most of the benefits of an ENC without having to
> maintain one.

That's one hell of a clever idea you got there! :D

> Our hiera hierarchy is pretty gross right now, since it's layered on top
> of what came with puppet_openstack_builder originally.  We don't use
> puppet environments. Since we have a puppet master per site &
> environment, we haven't had a need for them yet and I'm afraid of this
> bug: http://projects.puppetlabs.com/issues/12173

Thanks for pointing that one out. I didn't know about that particular bug.


More information about the OpenStack-operators mailing list