Re: [Openstack-operators] Nodes and configurations management in Puppet

2014-10-05 Thread Michael Dorman
On 10/3/14, 3:56 PM, "Mathieu Gagné" wrote: >On 2014-10-02 11:50 PM, Michael Dorman wrote: >> >> r10k >> deploys the Puppet environments (Œmaster¹ and Œprod¹ which correspond to >> git branches), heira data, and all the modules. Hiera data is in a >> separate (private) git repo, but there¹s only

Re: [Openstack-operators] Nodes and configurations management in Puppet

2014-10-03 Thread Mathieu Gagné
On 2014-10-02 11:50 PM, Michael Dorman wrote: r10k deploys the Puppet environments (Œmaster¹ and Œprod¹ which correspond to git branches), heira data, and all the modules. Hiera data is in a separate (private) git repo, but there¹s only a master branch there. Are people maintaining the manif

Re: [Openstack-operators] Nodes and configurations management in Puppet

2014-10-03 Thread Tim Bell
Proulx [mailto:j...@jonproulx.com] > Sent: 03 October 2014 18:01 > To: Michael Dorman > Cc: openstack-operators@lists.openstack.org > Subject: Re: [Openstack-operators] Nodes and configurations management in > Puppet > > We (http://www.csail.mit.edu) have a very complex (chaotic

Re: [Openstack-operators] Nodes and configurations management in Puppet

2014-10-03 Thread Jonathan Proulx
We (http://www.csail.mit.edu) have a very complex (chaotic) puppet world outside of OpenStack as we have dozens of research groups, each with servers and workstations that all need slightly different though mostly the same things along with "default" configs for these classes of systems and the var

Re: [Openstack-operators] Nodes and configurations management in Puppet

2014-10-02 Thread Michael Dorman
We maintain a fairly flat hiera structure, which largely is due to our OS infrastructure still being pretty simple. Like Clayton & Matt, we use a ³world² attribute to indicate dev/test/prod. (Although in hindsight, I like the Œechelon¹ term a lot better. We did the same exercise of thinking of s

Re: [Openstack-operators] Nodes and configurations management in Puppet

2014-09-27 Thread Michael Chapman
On Sat, Sep 27, 2014 at 4:03 AM, Mathieu Gagné wrote: > Hi Joe, > > Your experience and story about Puppet and OpenStack makes me feel like > you are a long lost co-worker. :) > > On 2014-09-25 10:30 PM, Joe Topjian wrote: > >> >> Hiera takes the cake for my love/hate of Puppet. I try really hard

Re: [Openstack-operators] Nodes and configurations management in Puppet

2014-09-26 Thread Mathieu Gagné
Hi Joe, Your experience and story about Puppet and OpenStack makes me feel like you are a long lost co-worker. :) On 2014-09-25 10:30 PM, Joe Topjian wrote: Hiera takes the cake for my love/hate of Puppet. I try really hard to keep the number of hierarchies small and even then I find it awkw

Re: [Openstack-operators] Nodes and configurations management in Puppet

2014-09-26 Thread Mathieu Gagné
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 deri

Re: [Openstack-operators] Nodes and configurations management in Puppet

2014-09-25 Thread John Dewey
On Thursday, September 25, 2014 at 7:30 PM, Joe Topjian wrote: > Hi Jay, > > Hiera takes the cake for my love/hate of Puppet. I try really hard to keep > the number of hierarchies small and even then I find it awkward sometimes. I > love the concept of Hiera, but I find it can be unintuitive. S

Re: [Openstack-operators] Nodes and configurations management in Puppet

2014-09-25 Thread Joe Topjian
Hi Jay, Hiera takes the cake for my love/hate of Puppet. I try really hard to keep the number of hierarchies small and even then I find it awkward sometimes. I love the concept of Hiera, but I find it can be unintuitive. Similar to the other replies, I have a "common" hierarchy where 90% of the da

Re: [Openstack-operators] Nodes and configurations management in Puppet

2014-09-25 Thread Fischer, Matt
On 9/25/14 7:40 AM, "Mathieu Gagné" wrote: >Hi, > >Some of you use Puppet to manage your OpenStack infrastructure. > >- How do you manage your node definitions? > Do you have an external ENC? > Or plain site.pp, Puppet Enterprise, theforeman, etc. ? We manage node definitions using hostnam

Re: [Openstack-operators] Nodes and configurations management in Puppet

2014-09-25 Thread Tim Bell
> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: 25 September 2014 20:12 > To: openstack-operators@lists.openstack.org > Subject: Re: [Openstack-operators] Nodes and configurations management in > Puppet > > On 09/25/2014 11:45 AM, J

Re: [Openstack-operators] Nodes and configurations management in Puppet

2014-09-25 Thread Jay Pipes
On 09/25/2014 11:45 AM, Joe Topjian wrote: Hi Mathieu, My setup is very similar to yours. Node definitions are in site.pp and Hiera is used for all configuration. The Hiera hierarchies are also very similar. Overall, I have a love/hate relationship with the setup. I could go on in detail, but i

Re: [Openstack-operators] Nodes and configurations management in Puppet

2014-09-25 Thread Clayton O'Neill
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

Re: [Openstack-operators] Nodes and configurations management in Puppet

2014-09-25 Thread Joe Topjian
Hi Mathieu, My setup is very similar to yours. Node definitions are in site.pp and Hiera is used for all configuration. The Hiera hierarchies are also very similar. Overall, I have a love/hate relationship with the setup. I could go on in detail, but it'd be all Puppet-specific rather than OpenSt