[ClusterLabs] agent ocf:pacemaker:controld

[Eric Ren]

Hello,

On 07/21/2016 09:31 PM, Da Shi Cao wrote:
> I've built the dlm_tool suite using the source from https://git.fedorahosted.org/cgit/dlm.git/log/.  The resource uisng ocf:pacemaker:controld will always fail to start because of timeout, even if start timeout is set to 120s! But if dlm_controld is first started outside the cluster management,  then the resource will show up and stay well!
1. Why do you suppose it's because of timeout? Any logs when DLM RA 
failed to start?
"ocf:pacemaker:controld" is bash script 
(/usr/lib/ocf/resource.d/pacemaker/controld).
If taking a look at this script, you'll find it suppose that 
dlm_controld is installed in a certain place (/usr/sbin/dlm_controld for
openSUSE). So, how would dlm RA find your dlm deamon?
> Another question is what's the difference of dlm_controld and gfs_controld? Must they both be present if a cluster gfs file system is mounted?
2. dlm_controld is a deamon in userland for dlm kernel module, while 
gfs2_controld is for gfs2, i think. However, on the recent release 
(redhat and suse, AFAIK),
gfs_controld is no longer needed. But I don't know much history about 
this change. Hope someone could elaborate on this a bit more;-)

Cheers,
Eric

>
> Thanks a lot!
> Dashi Cao
> ________________________________________
> From: Da Shi Cao <dscao999 at hotmail.com>
> Sent: Wednesday, July 20, 2016 4:47:31 PM
> To: Cluster Labs - All topics related to open-source clustering welcomed
> Subject: Re: [ClusterLabs] agent ocf:pacemaker:controld
>
> Thank you all for the information about dlm_controld. I will make a try using https://git.fedorahosted.org/cgit/dlm.git/log/ .
>
> Dashi Cao
>
> ________________________________________
> From: Jan Pokorný <jpokorny at redhat.com>
> Sent: Monday, July 18, 2016 8:47:50 PM
> To: Cluster Labs - All topics related to open-source clustering welcomed
> Subject: Re: [ClusterLabs] agent ocf:pacemaker:controld
>
>> On 18/07/16 07:59, Da Shi Cao wrote:
>>> dlm_controld is very tightly coupled with cman.
> Wrong assumption.
>
> In fact, support for shipping ocf:pacemaker:controld has been
> explicitly restricted to cases when CMAN logic (specifically the
> respective handle-all initscript that is in turn, in that limited use
> case, triggered from pacemaker's proper one and, moreover, takes
> care of dlm_controld management on its own so any subsequent attempts
> to do the same would be ineffective) is _not_ around:
>
> https://github.com/ClusterLabs/pacemaker/commit/6a11d2069dcaa57b445f73b52f642f694e55caf3
> (accidental syntactical typos were fixed later on:
> https://github.com/ClusterLabs/pacemaker/commit/aa5509df412cb9ea39ae3d3918e0c66c326cda77)
>
>>> I have built a cluster purely with
>>> pacemaker+corosync+fence_sanlock. But if agent
>>> ocf:pacemaker:controld is desired, dlm_controld must exist! I can
>>> only find it in cman.
>>> Can the command dlm_controld be obtained without bringing in cman?
> To recap what others have suggested:
>
> On 18/07/16 08:57 +0100, Christine Caulfield wrote:
>> There should be a package called 'dlm' that has a dlm_controld suitable
>> for use with pacemaker.
> On 18/07/16 17:26 +0800, Eric Ren wrote:
>> DLM upstream hosted here:
>>    https://git.fedorahosted.org/cgit/dlm.git/log/
>>
>> The name of DLM on openSUSE is libdlm.
> --
> Jan (Poki)
>
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>