I know this thread is over a year old and you may not care anymore,
but I was never satisfied with the answers I gave, so it stayed on my
todo list.
I've done some work recently improving the function for detecting when
to fence nodes and gracefully handling any non-pacemaker nodes that
are part o
On Fri, Mar 25, 2011 at 11:41 AM, Simone Gotti wrote:
> On 03/25/2011 11:10 AM, Andrew Beekhof wrote:
>> On Thu, Mar 17, 2011 at 11:54 PM, Simone Gotti
>> wrote:
>>> Hi,
>>>
>>> When using corosync + pcmk v1 starting both corosync and pacemakerd (and
>>> I think also using heartbeat or anything
On 03/25/2011 11:10 AM, Andrew Beekhof wrote:
> On Thu, Mar 17, 2011 at 11:54 PM, Simone Gotti wrote:
>> Hi,
>>
>> When using corosync + pcmk v1 starting both corosync and pacemakerd (and
>> I think also using heartbeat or anything other than cman) as quorum
>> provider, at startup in the CIB will
On Thu, Mar 17, 2011 at 11:54 PM, Simone Gotti wrote:
> Hi,
>
> When using corosync + pcmk v1 starting both corosync and pacemakerd (and
> I think also using heartbeat or anything other than cman) as quorum
> provider, at startup in the CIB will not be a entry for
> the nodes that are not in clus
On 03/17/2011 11:54 PM, Simone Gotti wrote:
> Hi,
>
> When using corosync + pcmk v1 starting both corosync and pacemakerd (and
> I think also using heartbeat or anything other than cman) as quorum
> provider, at startup in the CIB will not be a entry for
> the nodes that are not in cluster.
>
> In
Hi,
When using corosync + pcmk v1 starting both corosync and pacemakerd (and
I think also using heartbeat or anything other than cman) as quorum
provider, at startup in the CIB will not be a entry for
the nodes that are not in cluster.
Instead when using cman as quorum provider there will be a
