On Sep 4, 2008, at 10:06 AM, Paul Walsh wrote:
I think there's been a certain amount of confusion with regards to
Heartbeat and Pacemaker (and their versions), so I
wonder if those involved (Lars, Andrew, Alan?) would clarify the
following assumptions:
Pacemaker 0.6.x can be used as a replacement for the CRM in
heartbeat 2.1.3 (but NOT 2.1.4)?
Sort of. See link below.
As of 0.6.6 there is further overlap between Heartbeat and Pacemaker
that can't be removed with a configure option.
In future,
No. Not in the future, _now_.
both Heartbeat AND Pacemaker will be required to provide the
functional equivalent (broadly speaking) of 2.1.3 with its CRM, as
Heartbeat itself won't have a CRM?
Correct.
Pacemaker's NOT a fork or replacement for Heartbeat. If I
understand correctly, Pacemaker is so named because it's
required for Heartbeat to work in much the same as a pacemaker is
required to maintain a stable heart rhythm?
I think it might be worth highlighting the incompatibility between
Pacemaker and 2.1.4 (and *why*) on the Wiki page
http://www.clusterlabs.org/mw/Install
Is this sufficiently clear?
http://www.clusterlabs.org/mw/Install#READ_ME_FIRST
Under "First Steps" on that page, should
export STACKS_SUPPORTED="--with-ais-support --without-heartbeat-
support"
be
export STACKS_SUPPORTED="--without-ais-support --with-heartbeat-
support"
When building Heartbeat+Pacemaker?
yes
I assume the former applies when building OpenaAIS+Pacemaker
yes
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
