[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Cluster-devel] [Linux-HA] [Pacemaker] pcmk + corosync + cman for dlm support?



On 11/2/2011 2:23 PM, Nick Khamis wrote:
> I am actually buiding everything from source (glue, RA, pcmk,
> corosync/openais, dlm and friends),
> hoping that way I do not have to wait for the release of fedora 17
> (May 2012). I actually need this
> as soon as possible.

We always welcome patches and code contribution to speed things up.

Fabio

> 
> Nick
> 
> 
> On Wed, Nov 2, 2011 at 6:29 AM, Andrew Beekhof <andrew beekhof net> wrote:
>> On Wed, Nov 2, 2011 at 12:20 PM, Nick Khamis <symack gmail com> 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?
>>
>> Maybe fedora 17
>>
>>>
>>> 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?
>>>>>>
>>>>>> You may look at
>>>>>> http://www.mail-archive.com/pacemaker 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 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 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 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 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 lists linux-ha org
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
>>
> 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]