[Pacemaker] Corosync or Hearbeat or both ? (Re: Pacemaker Digest, Vol 40, Issue 67)

[José Pablo Méndez Soto]

Thanks Raoul,



 *José Pablo Méndez
     *********


2011/3/23 Raoul Bhatia [IPAX] <r.bhatia at ipax.at>

> On 03/23/2011 05:00 PM, José Pablo Méndez Soto wrote:
> > 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".
>
> if you use corosync + pacemaker, there is no need for heartbeat.
> (except for some libs - but this should correctly be handled via
> dependencies)
>
> e.g. my debian lenny box (with packages from backports):
> > # dpkg -l| egrep "corosync|heartbeat|pacemaker|stonith|cluster"
> > ii  cluster-agents     1:1.0.3-3~bpo50+1          The reusable cluster
> components for Linux HA
> > ii  cluster-glue       1.0.6-1~bpo50+1            The reusable cluster
> components for Linux HA
> > ii  corosync           1.2.1-1~bpo50+1            Standards-based cluster
> framework (daemon an
> > ii  libcluster-glue    1.0.6-1~bpo50+1            The reusable cluster
> components for Linux HA
> > ii  libcorosync4       1.2.1-1~bpo50+1            Standards-based cluster
> framework (libraries
> > ii  libheartbeat2      1:3.0.3-2~bpo50+1          Subsystem for
> High-Availability Linux (libra
> > ii  pacemaker          1.0.9.1+hg15626-1~bpo50+1  HA cluster resource
> manager
>
> cheers,
> raoul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110323/fc56ca3a/attachment.htm>