> -Original Message-
> From: Andrew Beekhof [mailto:and...@beekhof.net]
> Sent: Tuesday, 22 July 2014 12:07 PM
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] cloned resources
[snip]
> > I can do this
> >
> > pcs resource meta
prove that functionality :-(
>
> A
>
>
>> -Original Message-
>> From: Alex Samad - Yieldbroker [mailto:alex.sa...@yieldbroker.com]
>> Sent: Tuesday, 22 July 2014 11:30 AM
>> To: The Pacemaker cluster resource manager
>> Subject: Re: [Pacemaker]
esday, 22 July 2014 11:30 AM
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] cloned resources
>
> But I do want it to go over when there is an issue and to come back when
> that issue is fixed .
>
> I tried a move, but it doesn't work on in
uly 2014 11:17 AM
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] cloned resources
>
>
> On 22 Jul 2014, at 11:08 am, Alex Samad - Yieldbroker
> wrote:
>
> > Hi
> >
> > Online: [ alcdmz1 gsdmz1 ]
> >
> > Full list of
On 22 Jul 2014, at 11:08 am, Alex Samad - Yieldbroker
wrote:
> Hi
>
> Online: [ alcdmz1 gsdmz1 ]
>
> Full list of resources:
>
> Clone Set: proxyybip-clone [proxyybip] (unique)
> proxyybip:0(ocf::heartbeat:IPaddr2): Started alcdmz1
> proxyybip:1(ocf::heartbeat:
Hi
Let me expand
pcs config
Cluster Name: dmz
Corosync Nodes:
Pacemaker Nodes:
alcdmz1 gsdmz1
Resources:
Clone: proxyybip-clone
Meta Attrs: globally-unique=true clone-max=2 clone-node-max=2
Resource: proxyybip (class=ocf provider=heartbeat type=IPaddr2)
Attributes: ip=10.32.20.12
Hi
Online: [ alcdmz1 gsdmz1 ]
Full list of resources:
Clone Set: proxyybip-clone [proxyybip] (unique)
proxyybip:0(ocf::heartbeat:IPaddr2): Started alcdmz1
proxyybip:1(ocf::heartbeat:IPaddr2): Started gsdmz1
how can I turn off proxyybip:0 or how do I mov
06.10.2012 14:49, James Harper wrote:
> This is just a cosmetic thing, but I have a cloned resource that shows up
> like this:
>
> Clone Set: c_ping_X [p_ping_X]
> Started: [ node1 node2 ]
> Stopped: [ p_ping_X:0 p_ping_X:1 p_ping_X:4 ]
>
> That's correct in that the location restricti
This is just a cosmetic thing, but I have a cloned resource that shows up like
this:
Clone Set: c_ping_X [p_ping_X]
Started: [ node1 node2 ]
Stopped: [ p_ping_X:0 p_ping_X:1 p_ping_X:4 ]
That's correct in that the location restriction on the clone set c_ping_X only
allows it run on no
