Re: [ClusterLabs] pacemaker and fence_sanlock

2016-05-12 Thread Da Shi Cao
Hello Ken, Yes, I installed the fence_sanlock and fence_sanlockd in the same directory with corosync and pacemaker. There is no monitor action as listed from stonith_admin --meta --agent=fence_sanlock, and no monitor action from "crm_resource --show-metadata=stonith:fence_sanlock", either. So I

Re: [ClusterLabs] notify action asynchronous ?

2016-05-12 Thread Ken Gaillot
On 05/12/2016 04:37 AM, Jehan-Guillaume de Rorthais wrote: > Le Sun, 8 May 2016 16:35:25 +0200, > Jehan-Guillaume de Rorthais a écrit : > >> Le Sat, 7 May 2016 00:27:04 +0200, >> Jehan-Guillaume de Rorthais a écrit : >> >>> Le Wed, 4 May 2016 09:55:34 -0500,

Re: [ClusterLabs] Antw: Re: FR: send failcount to OCF RA start/stop actions

2016-05-12 Thread Ken Gaillot
On 05/12/2016 06:21 AM, Adam Spiers wrote: > Hi Ken, > > Firstly thanks a lot not just for working on this, but also for being > so proactive in discussing the details. A perfect example of > OpenStack's "Open Design" philosophy in action :-) > > Ken Gaillot wrote: >> On

Re: [ClusterLabs] Q: monitor and probe result codes and consequences

2016-05-12 Thread Ken Gaillot
On 05/12/2016 02:56 AM, Ulrich Windl wrote: > Hi! > > I have a question regarding an RA written by myself and pacemaker > 1.1.12-f47ea56 (SLES11 SP4): > > During "probe" all resources' "monitor" actions are executed (regardless of > any ordering constraints). Therefore my RA considers a

Re: [ClusterLabs] pacemaker and fence_sanlock

2016-05-12 Thread Ken Gaillot
On 05/11/2016 09:14 PM, Da Shi Cao wrote: > Dear all, > > I'm just beginning to use pacemaker+corosync as our HA solution on > Linux, but I got stuck at the stage of configuring fencing. > > Pacemaker 1.1.15, Corosync Cluster Engine, version '2.3.5.46-d245', and > sanlock 3.3.0 (built May 10

[ClusterLabs] Antw: Q: monitor and probe result codes and consequences

2016-05-12 Thread Ulrich Windl
>>> Ulrich Windl schrieb am 12.05.2016 um 09:56 in Nachricht <5734373F.4DE : >>> 161 : 60728>: > Hi! > > I have a question regarding an RA written by myself and pacemaker > 1.1.12-f47ea56 (SLES11 SP4): > > During "probe" all resources' "monitor" actions are executed (regardless of > any

Re: [ClusterLabs] Antw: Re: FR: send failcount to OCF RA start/stop actions

2016-05-12 Thread Adam Spiers
Hi Ken, Firstly thanks a lot not just for working on this, but also for being so proactive in discussing the details. A perfect example of OpenStack's "Open Design" philosophy in action :-) Ken Gaillot wrote: > On 05/10/2016 02:29 AM, Ulrich Windl wrote: > Ken Gaillot

Re: [ClusterLabs] Q: monitor and probe result codes and consequences

2016-05-12 Thread Kristoffer Grönlund
Ulrich Windl writes: > Should I mess with ocf_is_probe? That's probably the easiest way forward. Quite a few RAs have solved the problem in exactly that way (see the vmware RA for example). Cheers, Kristoffer > > Regards, > Ulrich > > > >

[ClusterLabs] Q: monitor and probe result codes and consequences

2016-05-12 Thread Ulrich Windl
Hi! I have a question regarding an RA written by myself and pacemaker 1.1.12-f47ea56 (SLES11 SP4): During "probe" all resources' "monitor" actions are executed (regardless of any ordering constraints). Therefore my RA considers a parameter as invalid ("file does not exist") (the file will be

[ClusterLabs] Antw: Re: Antw: Re: bug in crm shell (SLES11 SP4)? required parameters not checked

2016-05-12 Thread Ulrich Windl
>>> Lars Marowsky-Bree schrieb am 11.05.2016 um 16:13 in >>> Nachricht <20160511141305.gi...@suse.de>: > On 2016-05-11T08:02:56, Ulrich Windl > wrote: > >> > $ crm help Checks >> > $ crm options help check-frequency >> > $ crm options help