Re: [ClusterLabs] resource-stickiness

2015-08-27 Thread Rakovec Jost
Hi it doesn't work as I expected, I change name to: location loc-aapche-sles1 aapche role=Started 10: sles1 but after I manual move resource via HAWK to other node it auto add this line: location cli-prefer-aapche aapche role=Started inf: sles1 so now I have both lines: location cli-prefer

Re: [ClusterLabs] CRM managing ADSL connection; failure not handled

2015-08-27 Thread Tom Yates
On Mon, 24 Aug 2015, Andrei Borzenkov wrote: 24.08.2015 13:32, Tom Yates пишет: if i understand you aright, my problem is that the stop script didn't return a 0 (OK) exit status, so CRM didn't know where to go. is the exit status of the stop script how CRM determines the status of the stop

Re: [ClusterLabs] resource-stickiness

2015-08-27 Thread Ken Gaillot
On 08/27/2015 02:42 AM, Rakovec Jost wrote: > Hi > > > it doesn't work as I expected, I change name to: > > location loc-aapche-sles1 aapche role=Started 10: sles1 > > > but after I manual move resource via HAWK to other node it auto add this line: > > location cli-prefer-aapche aapche role=S

Re: [ClusterLabs] CRM managing ADSL connection; failure not handled

2015-08-27 Thread Ken Gaillot
On 08/27/2015 03:04 AM, Tom Yates wrote: > On Mon, 24 Aug 2015, Andrei Borzenkov wrote: > >> 24.08.2015 13:32, Tom Yates пишет: >>> if i understand you aright, my problem is that the stop script didn't >>> return a 0 (OK) exit status, so CRM didn't know where to go. is the >>> exit status of t

[ClusterLabs] Resources within a Group

2015-08-27 Thread Jorge Fábregas
Hi, I'm on SLES 11 SP4 (Pacemaker 1.1.12) and still learning all this :) I'm wondering if there's a way to control the resource startup behaviour within a group? For example, I have an LVM resource (to activate a VG) and the next one: the Filesystem resource (to mount it). If the VG activation f

[ClusterLabs] wait_for_all in SLES 11

2015-08-27 Thread Jorge Fábregas
Hi, Is there a way to recreate the newest Corosync option: wait_for_all in SLES 11? Does anyone (anyone from SUSE?) knows if there any plans to backport this into SLES 11? I can't say I miss this option (since I'm just starting out in HA) but after evaluating many possible situations with fence-

Re: [ClusterLabs] Resources within a Group

2015-08-27 Thread Andrew Beekhof
> On 28 Aug 2015, at 7:54 am, Jorge Fábregas wrote: > > Hi, > > I'm on SLES 11 SP4 (Pacemaker 1.1.12) and still learning all this :) > I'm wondering if there's a way to control the resource startup behaviour > within a group? > > For example, I have an LVM resource (to activate a VG) and the n

Re: [ClusterLabs] Antw: Re: fence_sanlock and pacemaker

2015-08-27 Thread Andrew Beekhof
> On 27 Aug 2015, at 4:20 pm, Ulrich Windl > wrote: > "Laurent B." schrieb am 27.08.2015 um 08:06 in > Nachricht > <55dea8cc.3080...@qmail.re>: >> Hello, >> >>> You’d have to build it yourself, but sbd could be an option >>> >> >> do you have any clue on how to install it on redhat (6.

Re: [ClusterLabs] Antw: Re: resource-stickiness

2015-08-27 Thread Andrew Beekhof
> On 27 Aug 2015, at 4:12 pm, Ulrich Windl > wrote: > Andrew Beekhof schrieb am 27.08.2015 um 00:20 in > Nachricht > : > >>> On 26 Aug 2015, at 10:09 pm, Rakovec Jost wrote: >>> >>> Sorry one typo: problem is the same >>> >>> >>> location cli-prefer-aapche aapche role=Started 10

Re: [ClusterLabs] wait_for_all in SLES 11

2015-08-27 Thread Digimer
Not a SUSE user, so I'm not familiar with what is shipped with SLES 11, but if it's corosync v2.x, you already have it. If it's not corosync v2, then you might be interested in how I solved this problem in RHEL 6 (corosync v1 + cman + rgmanager); 'safe_anvil_start' (https://github.com/digimer/stri

Re: [ClusterLabs] "0 Nodes configured" in crm_mon

2015-08-27 Thread Andrew Beekhof
> On 25 Aug 2015, at 1:45 am, Stanislav Kopp wrote: > > Hi all, > > I'm trying to run corosync2 + pacemaker setup on Debian Jessie (only > for testing purpose), I've successfully compiled all components using > this guide: http://clusterlabs.org/wiki/Compiling_on_Debian > > Unfortunately, if I

Re: [ClusterLabs] [ClusterLabs Developers] Resource Agent language discussion

2015-08-27 Thread Andrew Beekhof
> On 21 Aug 2015, at 2:21 am, Jehan-Guillaume de Rorthais > wrote: > > On Thu, 20 Aug 2015 15:05:24 +1000 > Andrew Beekhof wrote: > >> >>> On 19 Aug 2015, at 6:59 pm, Jehan-Guillaume de Rorthais >>> wrote: >>> >>> On Mon, 17 Aug 2015 09:42:35 +1000 >>> Andrew Beekhof wrote: >>> > On

Re: [ClusterLabs] Pacemaker tries to demote resource that isn't running and returns OCF_FAILED_MASTER

2015-08-27 Thread Andrew Beekhof
> On 21 Aug 2015, at 1:32 pm, Andrei Borzenkov wrote: > > 21.08.2015 00:35, Brian Campbell пишет: >> I have a master/slave resource (with a custom resource agent) which, >> if it uncleanly shut down, will return OCF_FAILED_MASTER on the next >> "monitor" operation. This seems to be what >> http:

Re: [ClusterLabs] Resources within a Group

2015-08-27 Thread Zhen Ren
Hi Jorge, Like "colocation" is what you want. Please take a look at here: http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-sets-colocation.html >>> > Hi, > > I'm on SLES 11 SP4 (Pacemaker 1.1.12) and still learning all this :) > I'm wondering if there's