[Pacemaker] Pacemaker Digest, Vol 40, Issue 67
José Pablo Méndez Soto
auxcri at gmail.com
Wed Mar 23 12:00:26 EDT 2011
Thank you Raoul,
It sounds to me then, as if Heartbeat was actually a remnant of old days. Is
there something Hearbeat does that Corosync can't? Why would I install
Heartbeat along Corosync? As you said, they are both "the messaging layer".
*José Pablo Méndez
> Message: 2
> Date: Wed, 23 Mar 2011 08:59:32 +0100
> From: "Raoul Bhatia [IPAX]" <r.bhatia at ipax.at>
> To: The Pacemaker cluster resource manager
> <pacemaker at oss.clusterlabs.org>
> Subject: Re: [Pacemaker] Corosync or Hearbeat or both ?
> Message-ID: <4D89A864.2020907 at ipax.at>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> On 23.03.2011 04:42, Jos? Pablo M?ndez Soto wrote:
> > Hi, I am recently starting to poke around with Pacemaker. Can someone
> > please explain what is the difference between Corosync and Heartbeat,
> > when would you use one or when the other? And why would you have
> > corosync installed accoring to this howto, if Heartbeat is to be the
> > preferred method? (the reason besides being a dependency):
> "heartbeat" was used for many different things, among them
> * messaging layer (= cluster communication)
> * resource agents (= resource management)
> * policy engine (= which resource is started where)
> since a couple of years, these specific tasks have been split
> into different (sub-)projects (e.g. pacemaker), and heartbeat has been
> "reduced" to be one messaging layer. corosync (formerly also known as
> openais) is another one.
> nowadays, most people seem to prefer corosync + pacemaker over
> heartbeat "v1" (legacy) or heartbeat + pacemaker.
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> End of Pacemaker Digest, Vol 40, Issue 67
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pacemaker