th1_1 \
> rule $id="p_VIPeth1_1_loc-rule" -inf: p_PINGDB lte 0
> location p_VIPeth1_1_loc2 p_VIPeth1_1 \
> rule $id="p_VIPeth1_1_loc2-rule" -inf: p_R_NODE1 eq Stopped
> property $id="cib-bootstrap-options" \
> dc-version="1.1.6-9971ebba449
-inf: clust1location
p_R_NODE2_pref p_R_NODE2 inf: clust2location p_VIPeth1_1_loc p_VIPeth1_1 \
rule $id="p_VIPeth1_1_loc-rule" -inf: p_PINGDB lte 0location p_VIPeth1_1_loc2
p_VIPeth1_1 \ rule $id="p_VIPeth1_1_loc2-rule" -inf: p_R_NODE1 eq
Stoppedproperty $id="cib-bootstrap-op
lient1
> / /|\
> DB>VIP |
>\|/
> Rnode2 ----> client2
>
>
>
> Maybe I should not have these resources grouped together since that implies
> collocation infinity for IP and rabbi
resource
>
>
> Steve
>
>
> From: and...@beekhof.net
> Date: Tue, 18 Mar 2014 11:44:34 +1100
> To: pacemaker@oss.clusterlabs.org
> Subject: Re: [Pacemaker] Don't want to stop lsb resource on migration
>
>
> On 14 Mar 2014, at 1:00 am, Bingham wrote:
s grouped together since that implies
collocation infinity for IP and rabbitmq?
Steve
From: and...@beekhof.net
Date: Tue, 18 Mar 2014 11:44:34 +1100
To: pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] Don't want to stop lsb resource on migration
On 14 Mar 2014, at 1:00 am,
On 14 Mar 2014, at 1:00 am, Bingham wrote:
> Hello,
>
> My setup:
> I have a 2 node cluster using pacemaker and heartbeat. I have 2
> resources, ocf::heartbeat:IPaddr and lsb:rabbitmq-server.
> I have these 2 resources grouped together and they will fail over to
> the
- Original Message -
> From: "Bingham"
> To: pacemaker@oss.clusterlabs.org
> Sent: Thursday, March 13, 2014 9:00:55 AM
> Subject: [Pacemaker] Don't want to stop lsb resource on migration
>
> Hello,
>
> My setup:
> I have a 2 node clust
Hello,
My setup: I have a 2 node cluster using pacemaker and heartbeat. I have
2 resources, ocf::heartbeat:IPaddr and lsb:rabbitmq-server.I
have these 2 resources grouped together and they will fail over to the other
node.
question: When rabbitmq is migrated to
