All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Dake <sdake@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] pcmk+corosync controld, dlm support without cman
Date: Wed, 02 Nov 2011 12:29:17 -0700	[thread overview]
Message-ID: <4EB19A0D.90102@redhat.com> (raw)
In-Reply-To: <CAGWRaZa9h+0=BHdM0MDD0eW+2Ku9MRVmS1vm_dOayF9GsNmnpA@mail.gmail.com>

On 11/01/2011 06:23 PM, Nick Khamis wrote:
> That would be really great. Is there any talk of when the next stable
> release of:
> * pcmk+corosync supporting direct communication with dlm gfs, controld
> * The separation of dlm, gfs, controld from cman
> 
> will be availabile?
> 
> Thanks in Advance,
> 
> Nick.
> 
> On Mon, Oct 31, 2011 at 4:52 AM, Andrew Beekhof <andrew@beekhof.net> wrote:
>> On Sat, Oct 29, 2011 at 3:09 AM, Nick Khamis <symack@gmail.com> wrote:
>>> Hello Gents,
>>>
>>> Thank you so much for your response. That being said, what are the
>>> plans once the next
>>> release of CMAN does not include PCMK and DLM related implementation? From what
>>> I can see, libdlm will be separated from the project completely.
>>
>> When CMAN goes away, the dlm gfs controld's will be talking directly
>> to corosync.
>> I believe the work has already been done but may need additional testing.
>>
>>>
>>> Thanks in Advance,
>>>
>>> Nick.
>>>
>>> On Fri, Oct 28, 2011 at 3:34 AM, Vladislav Bogdanov
>>> <bubble@hoster-ok.com> wrote:
>>>> 28.10.2011 04:04, Nick Khamis wrote:
>>>>> Hello Everyone,
>>>>>
>>>>> I just want to make sure this is still the case before I go through
>>>>> with it. I am trying to setup an
>>>>> active/active using:
>>>>>
>>>>> Corosync 1.4.2
>>>>> Pacemaker 1.1.6
>>>>> Cluster3
>>>>> DRBD 8.3.7
>>>>> OCFS2
>>>>>
>>>>> The only reason I installed Cluster3 was for dlm support. Fencing
>>>>> would be handled by stonithd.
>>>>> Is there any reason I need to fully install and configure two cluster
>>>>> managers. Defining nodes in
>>>>> both cman and corosync/openais?
>>>>

The developer community is targeting Fedora 17 for upstream integration
of this work.  Fedora 17 schedule hasn't been published and won't be
until F16 is finalized.  (next few weeks).  I expect other distros will
follow on once the dust settles.

Regards
-steve
.
>>>> You may look at
>>>> http://www.mail-archive.com/pacemaker at oss.clusterlabs.org/msg09959.html
>>>>
>>>> That message contains Andrew's dlm_controld patch for shortening fencing
>>>> path - it now talks directly to stonith subsystem, rebased for 3.0.17,
>>>> and some fixes to make it all compile. Some work should probably be done
>>>> to make it apply/compile on latest cluster3.
>>>>
>>>> That way I eliminate cman from stack (except some dlm-related libs) and
>>>> run cluster with stable fencing on top of corosync/openais.
>>>>
>>>> Best,
>>>> Vladislav
>>>> _______________________________________________
>>>> Linux-HA mailing list
>>>> Linux-HA at lists.linux-ha.org
>>>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>>>> See also: http://linux-ha.org/ReportingProblems
>>>>
>>> _______________________________________________
>>> Linux-HA mailing list
>>> Linux-HA at lists.linux-ha.org
>>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>>> See also: http://linux-ha.org/ReportingProblems
>>>
>> _______________________________________________
>> Linux-HA mailing list
>> Linux-HA at lists.linux-ha.org
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
>>
> 



  reply	other threads:[~2011-11-02 19:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02  1:23 [Cluster-devel] pcmk+corosync controld,dlm support without cman Nick Khamis
2011-11-02 19:29 ` Steven Dake [this message]
2011-11-02 19:41   ` [Cluster-devel] pcmk+corosync controld, dlm " Nick Khamis
2011-11-03 12:54     ` Andrew Beekhof
2011-11-03 13:03       ` Nick Khamis

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=4EB19A0D.90102@redhat.com \
    --to=sdake@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.