On 03/01/2012 07:19 AM, Lars Marowsky-Bree wrote:
> On 2012-03-01T09:52:29, Florian Haas wrote:
>
>> Future situation (Pacemaker with Corosync 2.x):
>> - OpenAIS goes away, no CKPT service, ocfs2_controld.pcmk stops working;
>> - cman goes away, ocfs2_controld.cman stops working.
>>
>> Is that su
On 2012-03-01T09:52:29, Florian Haas wrote:
> Future situation (Pacemaker with Corosync 2.x):
> - OpenAIS goes away, no CKPT service, ocfs2_controld.pcmk stops working;
> - cman goes away, ocfs2_controld.cman stops working.
>
> Is that summary correct?
>
> Do you happen to know whether the OCFS
On Thu, Mar 1, 2012 at 12:11 AM, Andrew Beekhof wrote:
> On Thu, Mar 1, 2012 at 8:08 AM, Florian Haas wrote:
>> Andrew,
>>
>> just a quick question out of curiosity: the ocf:pacemaker:o2cb resource
>> and ocfs2_controld.pcmk require the OpenAIS CKPT service which is
>> currently deprecated (as al
On Thu, Mar 1, 2012 at 8:08 AM, Florian Haas wrote:
> Andrew,
>
> just a quick question out of curiosity: the ocf:pacemaker:o2cb resource
> and ocfs2_controld.pcmk require the OpenAIS CKPT service which is
> currently deprecated (as all of OpenAIS) and going away completely
> (IIUC) with Corosync
Andrew,
just a quick question out of curiosity: the ocf:pacemaker:o2cb resource
and ocfs2_controld.pcmk require the OpenAIS CKPT service which is
currently deprecated (as all of OpenAIS) and going away completely
(IIUC) with Corosync 2.0. Does that mean that OCFS2 will be unsupported
from Corosync
