Puppet users - Nov 2011 - Recommended/Best Practise directory structure for a multi domain setup

Looking into deploying puppet in work environment only thing which i
am trying to work out is a good directory structure which we can use
and then commit changes into subversion (cant use git need to use our
existing source control system).

To make things complicated we have multiple data centres, and within
these data centres we have a production and staging environment within
them and with one data centre we have dev/qa/staging environments.

Any help or surgestions would be greatly appricated. I am already
reading up on environments within puppet but would like to get peoples
opinions and experiences in this.

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

We have a single Puppet master for every data center. Every master has its own
Subversion branch containing the appropriate Puppet configuration along with the
environments needed. It''s quite an easy concept which works very well
for us and which also allows managing configurations between the data centers by
doing some appropriate SVN-merges.

Bernd
> -----Ursprüngliche Nachricht-----
> Von: puppet-users@googlegroups.com [mailto:puppet-
> users@googlegroups.com] Im Auftrag von PaulC
> Gesendet: Freitag, 25. November 2011 13:06
> An: Puppet Users
> Betreff: [Puppet Users] Recommended/Best Practise directory structure
> for a multi domain setup
> 
> Looking into deploying puppet in work environment only thing which i
> am trying to work out is a good directory structure which we can use
> and then commit changes into subversion (cant use git need to use our
> existing source control system).
> 
> To make things complicated we have multiple data centres, and within
> these data centres we have a production and staging environment within
> them and with one data centre we have dev/qa/staging environments.
> 
> Any help or surgestions would be greatly appricated. I am already
> reading up on environments within puppet but would like to get peoples
> opinions and experiences in this.
> 
> --
> You received this message because you are subscribed to the Google
> Groups "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to puppet-
> users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Using a unique branch per site is probably the wrong move since it
really doesn''t consolidate anything. All it does is move all the
redundancy a bit further upstream. A better solution is to put more
thought into your source tree''s directory structure in order to
support site-specific bits where needed. I gave a presentation about
this very topic at PuppetConf a few months ago. Just search for Adam
Kosmin PuppetConf and you should find it.

Best,
Adam

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.