[adding sanlock-devel ML into the loop as deemed appropriate]
On 18/05/16 12:49 +, Da Shi Cao wrote:
> After some try and error, fence_sanlock can be used as a stonith
> resource in pacemaker+corosync.
> 1. Add a "monitor" action, which is exactly the same action as
> "status".
Per
Hello everybody,
After some try and error, fence_sanlock can be used as a stonith resource in
pacemaker+corosync.
1. Add a "monitor" action, which is exactly the same action as "status".
2. Make "status" action return "false" if a resource belongs to a host is
acquired and owned by another host.
Gents,
I'm trying to configure a HA cluster with RHEL 6.5. Everything goes well
except the fencing. The cluster's node are not connected to the
management lan (where stand all the iLO/UPS/APC devices) and it's not
planned to connecting them to this lan.
With these constraints, I figured out that
On 27 Aug 2015, at 4:11 am, Laurent B. laure...@qmail.re wrote:
Gents,
I'm trying to configure a HA cluster with RHEL 6.5. Everything goes well
except the fencing. The cluster's node are not connected to the
management lan (where stand all the iLO/UPS/APC devices) and it's not
planned
