We've started to feel the pain of this so have just got a process running.
The main puppet tree lives in svn and consists of the majority of
service modules, we're only deploying to CentOS boxes so this makes it
relatively easy. We have:
* two environments - development, production
* three pupp
I wanted to post sooner ... oh well... This is resonably complicated and
easier understood on the whiteboard in my office :)
Our build processes uses 3 environments, noop setting, SVN, inventory fakedb
(csv file), and custom reports
*ENVs*
1. *dev* - separate server, you can do whatever you w
I try to explain how we implemented our workflow.
We developed some strategies to make puppet module development easy to test
and we have a way to rollout our configuration to different environments by
simply taging the versions we think they are stable enough. Basically we use
the power of th
Ok, I'll bite :)
warning: this is going to be long and complicated, i think this is the part
which was most challenging in setting up our puppet infrastructure.
some background and assumptions:
- we have many sites / locations / data centers.
- we have many different host types (e.g. server prof
On Fri, Jul 17, 2009 at 1:06 PM, Teyo Tyree wrote:
> In the course of training and consulting with Puppet, the question of change
> management best practices has come up over and over again. On the edges, we
> have small teams that can get away with simply version controlling their
> code using a
- "Teyo Tyree" wrote:
> In the course of training and consulting with Puppet, the question of
> change management best practices has come up over and over again. On
> the edges, we have small teams that can get away with simply version
> controlling their code using an SCM as an incremental
Hi,
> In the course of training and consulting with Puppet, the question of
> change management best practices has come up over and over again. On
> the edges, we have small teams that can get away with simply version
> controlling their code using an SCM as an incremental backups while
> rollin
On Fri, Jul 17, 2009 at 1:06 PM, Teyo Tyree wrote:
> In the course of training and consulting with Puppet, the question of
> change management best practices has come up over and over again. On the
> edges, we have small teams that can get away with simply version controlling
> their code using
