On Tue, 21 Aug 2012, Jon Heese wrote: >> On 21 Aug 2012, at 22:06, David Lang <david_l...@intuit.com> wrote: >> Well haproxy does all that out of the box, no tricks or tweakery >> required... >> >> Another thing I like about haproxy is that it's unnervingly fast; >> start/stop/reload are effectively instantaneous... >> >> I'm running heartbeat + pacemaker/crm at the moment. I've had a couple >> of attempts at migrating to corosync, but so far I've had no success >> and a great deal of confusion, even though all I'm doing is managing a >> single IP... > > Feel free to keep discussing alternatives, but I am not at liberty to change > this system from the current Heartbeat/Pacemaker/CRM architecture. > > Does anyone have any ideas about making my setup do what I'm asking? Any > comments on my idea of switching to OCF and hacking the resource script to > never run the "stop" command (except maybe on shutdown or some other cases > that I haven't thought of yet ;))?
The simple answer is to just not have heartbeat manage Apache. Start Apache from the standard system-wide init scripts (or systemd, upstart, etc) Heartbeat doesn't need to know that Apache exists for this to work. What you loose is the ability for heartbeat to notice that Apache is down and failover from that system, but in my experience that's not a very valuable capability in the first place (the number of outages caused by Apache going down is dwarfed by the number of outages caused by the application not working, when Apache is healthy) David Lang _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
