Either use a local proxy or load balancer or use a wrapper script that checks which pm is alive and then execute puppet with the correct --server option
Ohad On 5/14/09, Greg <greg.b...@gmail.com> wrote: > > Hi guys, > > I have a multi-site setup that I am configuring to manage via Puppet. > At present > there is only a single puppetmaster, but I'm about to set up a second > one at > another site for redundancy and to speed up requests by keeping the > configuration > at the one site. > > I want to set up Puppet clients to first attempt to connect to the > puppetmaster > at their local site and if that fails to try the puppetmaster at the > alternate site. > Obviously this requires the puppetmaster configurations to be > identical - no problem. > The problem is that I can only set one server name into the > puppet.conf file, I can't > specify a list. > > I know some people have gotten around this (sort of) by using Apache > and mod_proxy > to load balance the configuration - that's not what I'm after, its not > a load issue, its a > redundancy issue I'm trying to solve. All that putting in Apache or > some other load > balancer does is move the point of failure. > > Also, putting in multiple A records in DNS doesn't help, as that gives > a round-robin > approach - I want the clients to favour the server for their > particular site. > > Any thoughts on how to work this would be appreciated. > > > --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
