On 04/10/15 18:23, Richard Gray wrote:
On 03/10/15 13:08, Joao Morais wrote:
How to manage a Puppet Server with multi-environment and multi-system?
Rather than having puppet environments that correspond to
physical environments, the single production Puppet environment
represents the stable tested version of our Puppet code and Hiera
config.
Hi. Your model sounds interesting and I think that we would use
something like that in our company. Our main problem is that we want to
manage a really big bunch of unrelated systems. An example: something
will change in the system-A configuration, so this change is (or these
changes are) versioned in branch devel. After tests the change(s) should
be merged to prod, but only changes made to system-A. Since devel is
shared between other systems I cannot do it in an automated or a non
error prone way.
We are planning to split every system configuration into different repos
in order to have a more cohesive repository, but we don't know yet if
this is the right move and how to do it in an easy to manage way.
Gary Larizza describes a similar model, more cogently than I have, in a
blog post here:
http://garylarizza.com/blog/2014/03/26/random-r10k-workflow-ideas/
Yeah, our r10k model started with these and other Garry's readings.
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/56125B13.4080005%40joaomorais.com.br.
For more options, visit https://groups.google.com/d/optout.
