[Pacemaker] Pacemaker in RHEL6.

[Andrew Beekhof]

On Fri, Aug 12, 2011 at 6:04 PM, Marco van Putten
<marco.vanputten at tudelft.nl> wrote:
> On 08/12/2011 06:05 AM, Larry Brigman wrote:
>>
>> On Thu, Aug 11, 2011 at 8:51 PM, Larry Brigman <larry.brigman at gmail.com
>> <mailto:larry.brigman at gmail.com>> wrote:
>>
>>    On Thu, Aug 11, 2011 at 5:37 PM, Andrew Beekhof <andrew at beekhof.net
>>    <mailto:andrew at beekhof.net>> wrote:
>>
>>        On Fri, Aug 12, 2011 at 1:13 AM, Larry Brigman
>>        <larry.brigman at gmail.com <mailto:larry.brigman at gmail.com>> wrote:
>>         > On Wed, Aug 10, 2011 at 10:50 PM, Marco van Putten
>>         > <marco.vanputten at tudelft.nl
>>        <mailto:marco.vanputten at tudelft.nl>> wrote:
>>         >>
>>         >> On 08/10/2011 06:23 PM, David Coulson wrote:
>>         >>>
>>         >>> On 8/10/11 11:43 AM, Marco van Putten wrote:
>>         >>>>
>>         >>>> Thanks Andreas. But our managers persist on using Redhat.
>>         >>>
>>         >>> I think the idea would be to take the HA packages
>>        distributed with
>>         >>> Scientific Linux 6.x and run them on RHEL.
>>         >>
>>         >>
>>         >> OK Thanks for the heads up. I will give it a try with the
>>        Scientific Linux
>>         >> packages on RHEL.
>>         >>
>>         >>
>>         >>>
>>         >>> Note that even when you do subscribe to the HA add-on in
>> RHEL6,
>>         >>> pacemaker is not supported by RedHat. Are you sure you
>>        can't buy the HA
>>         >>> add-on to go with your base entitlement for RHEL?
>>         >>
>>         >>
>>         >> No unfortunately Redhat's license model doesn't work that
>>        way. In stead of
>>         >> the 150$ academic license you have to buy the full licensed
>>        version and then
>>         >> some extra for the add-on.
>>         >>
>>         > If you have the install DVD then the packages are there, just
>>        in a different
>>         > repo on the disk.
>>         > Directory is HighAvailability.
>>         >  ls pacemaker-*
>>         > pacemaker-1.1.2-7.el6.x86_64.rpm
>>        pacemaker-libs-1.1.2-7.el6.i686.rpm
>>         > pacemaker-libs-1.1.2-7.el6.x86_64.rpm
>>
>>        Is corosync and cluster-glue in there too?
>>
>>    Yes.
>>    Packages]$ ls coro*
>>    corosync-1.2.3-21.el6.x86_64.rpm   corosynclib-1.2.3-21.el6.x86_64.rpm
>>    corosynclib-1.2.3-21.el6.i686.rpm
>>      Packages]$ ls cluster*
>>    cluster-cim-0.16.2-10.el6.x86_64.rpm
>>    clusterlib-3.0.12-23.el6.i686.rpm
>>    cluster-glue-1.0.5-2.el6.x86_64.rpm
>>    clusterlib-3.0.12-23.el6.x86_64.rpm
>>    cluster-glue-libs-1.0.5-2.el6.i686.rpm
>>    cluster-snmp-0.16.2-10.el6.x86_64.rpm
>>    cluster-glue-libs-1.0.5-2.el6.x86_64.rpm
>>
>>
>> The source packages are also available.
>> ftp://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/
>>
>>
>
>
> I also found the rpm's on our Redhat satellite server. But this doesn't make
> it much easier if you want to do a upgrade to a newer version.
>
> I've tried the Scientific Linux way by adding it as a disabled repository.
>
> And then installing pacemaker by:
> # yum install --enablerepo=scientificlinux pacemaker
>
> Yum then takes care of all the dependencies and (somehow) only uses the
> pacemaker/corosync/etc packages from scientific while the rest comes from
> Redhat. You still need the epel repository as well btw.
>
> So The Scientific Linux option works best for our situation I think.
>
> Thanks everyone for all the reply's,
> Marco.

I've written this up for the wiki:
   http://clusterlabs.org/wiki/RHEL