Hi Mike,
I'm not sure if your after puppet-specific methods, or just general
systems for this?
When we set up our load balancing and DR, we preferred to keep it
simple, the methods used are outlined below.
1) Site code - This is managed but subversion, we maintain separate
repositories for test
one rather rough solution I've used for this before, is a separate
monitoring daemon, that polls the primary server on a regular basis, if
this falls over, the daemon then can use 1 of 2 approaches
1) Rewrite the IP for the hostname of the puppetmaster in the /etc/hosts
file (really rough, but doe