[Pacemaker] Dropping HeartBeat Stack?

[Andrew Beekhof]

On Wed, Mar 3, 2010 at 4:00 PM, Dennis J. <dennisml at conversis.de> wrote:
> On 03/03/2010 09:24 AM, Andrew Beekhof wrote:
>>
>> On Wed, Mar 3, 2010 at 1:16 AM, Angie T. Muhammad
>> <angie.tawfik at gmail.com>  wrote:
>>>
>>> Hello list
>>>
>>> I have no technical questions at the moment, just a couple of
>>> distribution-specific and backward compatibility questions..
>>>
>>> 1- I just wonder will Pacemaker at any time in the near future (the next
>>> two
>>> years) drop HeartBeat as a cluster stack?
>>
>> The overhead for supporting it is minimal, and as yet there are no
>> core features that can't be implemented for Heartbeat as well.
>> If either of those two things change, then we would have to
>> re-evaluate how best support Heartbeat in the following release
>> series.
>>
>> There are no plans to change anything for the upcoming 1.1 and 1.2
>> release series (ie. the next 2-3 years).
>>
>>> 2- Andrew, when shall we see Pacemaker in RHEL instead of Redhat Cluster
>>> Suite?
>>
>> Red Hat has a very strict policy about discussing what "may or may not
>> be part of a current and/or future Red Hat products".
>> Having said that, I got approval to include the following in an
>> abstract I submitted for this years Red Hat Summit:
>>
>>   "Pacemaker is the scalable High-Availability cluster resource
>> manager intended to be the successor to rgmanager."
>>
>> Although I doubt using it on top of Heartbeat would ever be an option.
>
> If corosync/openais is the preferred option nowadays why is heartbeat chosen
> as default when installing the RPMs from clusterlabs.org?

What do you mean by default?
Neither cluster stack is installed by default if you just do:
  yum install pacemaker

you have to explicitly specify either corosync or heartbeat

> The service is
> even activated after the install even though no workable config file is
> included.

Good point.