On Fri, Nov 13, 2009 at 9:07 AM, mcn...@cafes.net wrote:
>
> I have two different networks that I'm managing. I would like to set up a
> puppetmaster for each network.
>
In this case, I would recommend the following to simplify things:
1. Use revision control (svn, git, etc.) to manage all of
mcn...@cafes.net wrote:
> I have two different networks that I'm managing. I would like to set up a
> puppetmaster for each network, but it would be nice if I could set up a
> master/slave relationship somehow between the two puppetmasters so that I only
> have to make changes to one of them and
In this case I would recommend using distributed revision control, for
example git or mercurial. Syncronizing between several hosts is what
these does well.
In my case, I use mercurial on a virtual machine I use for development
in my puppet environment. When I'm happy with how it's working on all
You probably also want a development environment when you'll write/
test your manifests. This could be hooked into a VCS. You'll develop
in a testing branch and merge your tested code into trunk. From there,
you can rsync trunk over to /etc/puppet on each of your 'production'
puppet masters.
Pers
I have two different networks that I'm managing. I would like to set up a
puppetmaster for each network, but it would be nice if I could set up a
master/slave relationship somehow between the two puppetmasters so that I only
have to make changes to one of them and have it pushed to both networks.
Could you tell us a bit more about what it is you are trying to do?
Puppet contains several components, so replication can mean many
things. Are you for example just looking to synchronize modules across
several puppetmasters, a revision control tool might be what you want.
If you're looking to a
