On 08/21/2012 03:06 PM, David Lang wrote: > On Tue, 21 Aug 2012, Marcus Bointon wrote: >> >> I've done this for years with haproxy by allowing non-local binding: > > I've been doing the same thing. Failovers work much faster when all you need > to > do is to move the IP and not start/stop software > >> I've never figured out why people use heartbeat to 'manage' the web front >> end when it can just stay running. If haproxy is pointing at multiple web >> servers, it can deal with monitoring, failover and balancing for them. > > One legitimate reason for doing this is that you can then have heartbeat > 'monitor' the webserver and if the webserver dies, initiate a failover.
Running more than just apache would be another: I usually also have vsftpd and document root on drbd drive. > I still have most systems using the version 1 style haresources config. It's > great for doing the simple failover scenario easily. Me too, only s/most/all/. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
