[Pacemaker] CRM and openAIS

Andrew Beekhof beekhof at gmail.com
Fri Jan 11 15:02:31 EST 2008


On Jan 11, 2008, at 7:43 PM, Serge Dubrouski wrote:

>>>> can you do an ls of /usr/lib/lcrso for me pls?
>>>> looks like the plugin cant be found or wont load
>>>
>>> # ls /usr/lib/lcrso
>>> ls: /usr/lib/lcrso: No such file or directory
>>
>> s/lib/libexec/ ?
>> i forget what defaults are for red hat
>
> [sdubrov at fc-node1 ~]$ ls -l /usr/libexec/lcrso/
> total 972
> -rwxr-xr-x 1 root root  15602 Dec 12 11:46 aisparser.lcrso
> -rwxr-xr-x 1 root root  26982 Dec 12 11:46 objdb.lcrso
> -rwxr-xr-x 1 root root 432973 Dec 12 11:46 service_amf.lcrso
> -rwxr-xr-x 1 root root  23977 Dec 12 11:46 service_cfg.lcrso
> -rwxr-xr-x 1 root root 116878 Dec 12 11:46 service_ckpt.lcrso
> -rwxr-xr-x 1 root root  35638 Dec 12 11:46 service_clm.lcrso
> -rwxr-xr-x 1 root root  44795 Dec 12 11:46 service_cpg.lcrso
> -rwxr-xr-x 1 root root  23590 Dec 12 11:46 service_evs.lcrso
> -rwxr-xr-x 1 root root 114247 Dec 12 11:46 service_evt.lcrso
> -rwxr-xr-x 1 root root  60107 Dec 12 11:46 service_lck.lcrso
> -rwxr-xr-x 1 root root  48487 Dec 12 11:46 service_msg.lcrso
> -rwxr-xr-x 1 root root  23814 Dec 12 11:46 vsf_ykd.lcrso
> [sdubrov at fc-node1 ~]$
>

looks like the pacemaker plugin is missing :-(

i'll fix that tomorrow.  in the meantime, if service_crm.so is part of  
the package somewhere, copy it to the above directory with a .lcrso  
suffix and restart ais...
it should "just work"

>
>>
>>>>> 7. None of the installed packages included ocf RAs. How is it
>>>>> supposed
>>>>> to run resources?
>>>>
>>>> they're in heartbeat-resources
>>>>
>>>> though i'm not 100% sure breaking them out into their own package
>>>> is a
>>>> good idea.  thoughts?
>>>
>>> I'm kind of disagree. Without them CRM is almost useless,
>>
>> well in theory the Red Hat (or anyone else) could supply their own  
>> set
>> of RAs which could be used instead
>>
>>> so I'd put them into pacemaker-openais.
>>
>> Even if I wanted to (which I'm not convinced I do), there are
>> political problems with doing so and we would start having double
>> maintenance issues.
>> If anything, I'd merge heartbeat-resources with heartbeat-common.
>>> I take it that at the end you are going to get rid of heartbeat-
>>> common.
>>
>> no, no plans for that.
>
> That creates some kind of a confusion at least in the naming of
> packages. Why would I need a heartbeat package if I'm going to use
> openAIS + CRM?

heartbeat-common contains a number of useful libraries and tools (such  
as the lrmd) which are useful regardless of which cluster stack one is  
using.
In fact clplumbing is useful even if you're not doing clustering at  
all - there is a lot of good stuff in there.

> So I'd name them pacemaker-base and pacemaker-openais.
> But I'm agree that it creates political issues :-)

More than anything else, its also not accurate, since the package  
comes from the heartbeat project not pacemaker.

I could try and maintain those parts of the code in pacemaker but I  
don't have the intention, time or expertise to do so.
There is simply no benefit in trying to.

Everyone repeat after me... Pacemaker is NOT a fork of Heartbeat.  The  
project contains the CRM and nothing more.




More information about the Pacemaker mailing list