From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Error when compiling dlm from cman
Date: Wed, 26 Oct 2011 20:19:39 +0200 [thread overview]
Message-ID: <4EA84F3B.9060306@redhat.com> (raw)
In-Reply-To: <CAGWRaZa738uQmNHbtuDp8oCudG_o3K86FPNKpsCt017ZRvvgTg@mail.gmail.com>
On 10/26/2011 8:17 PM, Nick Khamis wrote:
> I forgot to ask:
>
>>> Yes that is correct. dlm_controld.pcmk has been obsoleted in favour of
>>> cman support for pacemaker.
>
> Does that mean that dlm + fence is provided by cman directly, and thus
> deprecating libdlm?
no. libdlm is still required.
>
> I just want to make sure I am on the right page. I would like to
> provide dlm and fence
> capabilities for our pcmk cluster.
>
It means that pacemaker can use cman to obtain cluster view and quorum
info. So you basically configure cman and then run pacemaker instead of
rgmanager.
> Thanks Again,
>
> Nick
>
> On Wed, Oct 26, 2011 at 2:12 PM, Nick Khamis <symack@gmail.com> wrote:
>> Fabio,
>>
>> I appologize for that. It was unintentional. If you notice, I said
>> "Hello Gents". I will upgrade to 1.4.2, and
>> keep everyone posted.
>>
>> Thanks Again,
>>
>> Nick.
>>
>> On Wed, Oct 26, 2011 at 2:09 PM, Fabio M. Di Nitto <fdinitto@redhat.com> wrote:
>>> (please keep cluster-devel in the CC list, it might be helpful for other
>>> people too)
>>>
>>> On 10/26/2011 3:00 PM, Nick Khamis wrote:
>>>> Hello Gents,
>>>>
>>>> Thank you so much for your responses! There use to be
>>>> "--enable-pacemaker" "--disable-cman"
>>>> flags. These have since been dropped. So just build everything in
>>>> Cluster 3 even for the pcmk stack?
>>>
>>> Yes that is correct. dlm_controld.pcmk has been obsoleted in favour of
>>> cman support for pacemaker.
>>>
>>>>
>>>> Any idea on the following fence error:
>>>>
>>>> /src/cluster-3.1.7/fence/fenced/config.c
>>>> In file included from /usr/local/src/cluster-3.1.7/fence/fenced/config.c:1:
>>>> /usr/local/src/cluster-3.1.7/fence/fenced/fd.h:182: error: field
>>>> cpg_ringid has incomplete type
>>>> make[2]: *** [config.o] Error 1
>>>> make[2]: Leaving directory `/usr/local/src/cluster-3.1.7/fence/fenced'
>>>> make[1]: *** [all] Error 2
>>>> make[1]: Leaving directory `/usr/local/src/cluster-3.1.7/fence'
>>>> make: *** [fence] Error 2
>>>>
>>>> I am prototyping on a debian VM, and will be using fence_virt. For
>>>> production, we will move to
>>>> RH and obviously a STONITH device.
>>>>
>>>> Thanks in Advance,
>>>>
>>>> Nick from Toronto.
>>>
>>> You need a newer version of corosync. I don?t recall exactly what
>>> version introduces the cpg_ringid, but you are better off taking 1.4.2.
>>>
>>> Fabio
>>>
>>
next prev parent reply other threads:[~2011-10-26 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 1:47 [Cluster-devel] Error when compiling dlm from cman Nick Khamis
2011-10-26 2:59 ` Bob Peterson
2011-10-26 3:25 ` Fabio M. Di Nitto
[not found] ` <CAGWRaZZPDoXRcTUjSgWBWVXZQeDU-btkcpOgqwX7uw=MdqnOmQ@mail.gmail.com>
2011-10-26 18:09 ` Fabio M. Di Nitto
2011-10-26 18:12 ` Nick Khamis
2011-10-26 18:14 ` Fabio M. Di Nitto
2011-10-26 18:17 ` Nick Khamis
2011-10-26 18:19 ` Fabio M. Di Nitto [this message]
2011-10-26 18:29 ` Nick Khamis
2011-10-26 18:34 ` Nick Khamis
2011-10-26 18:36 ` Fabio M. Di Nitto
2011-10-26 18:38 ` Nick Khamis
2011-10-26 18:41 ` Fabio M. Di Nitto
2011-10-26 20:46 ` Nick Khamis
2011-10-26 18:34 ` Fabio M. Di Nitto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EA84F3B.9060306@redhat.com \
--to=fdinitto@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).