Hi,
crm has a nice placement constraint syntax
location loc1 res1 inf: node1
which is a shortcut for
location loc1 res1 inf: rule #uname eq node1
Sometimes, in otherwise symmetric cluster, there are some resources that have
to be running on a certain node,
so one has to create an anti-placem
Dejan,
Well, I will got back to plan B and use the power splitter.
Thanks,
Rick
-Original Message-
From: Dejan Muhamedagic [mailto:deja...@fastmail.fm]
Sent: Tuesday, November 16, 2010 3:24 AM
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] Stonith Device APC AP7900
Hi Andrew,
Thanks for reply.
I confirmed it.
Regards,
Tomo
2010/11/20 Andrew Beekhof
> On Fri, Nov 19, 2010 at 8:48 AM, nozawat wrote:
> > Hi
> >
> > I output log in /var/log/ha.log by the following setting.
> > It is not output by /var/log/ha.log when I operate this with a V1 mode.
> >
On Mon, Nov 15, 2010 at 6:34 PM, Alan Jones wrote:
> primitive resX ocf:pacemaker:Dummy
> primitive resY ocf:pacemaker:Dummy
> location resX-nodeA resX -inf: nodeA.acme.com
> location resY-loc resY 1: nodeB.acme.com
> colocation resX-resY -2: resX resY
>
> Both resX and resY end up on nodeB. I'm
On Fri, Nov 19, 2010 at 10:11 AM, JiaQiang Xu wrote:
> Hi,
>
> I'm using pacemaker 1.0.9 and corosync 1.2.7.
> Recently I found a problem with CRMD restart.
>
> If CRMD crashes or is manually killed, for now corosync will try to restart it
> up to 100 times (done in lib/ais/plugin.c). But what if
On Fri, Nov 19, 2010 at 8:48 AM, nozawat wrote:
> Hi
>
> I output log in /var/log/ha.log by the following setting.
> It is not output by /var/log/ha.log when I operate this with a V1 mode.
> In the case of a V1 mode, is not setting enough?
It should be. Summarizing from mcp/corosync.c
ge
