[Pacemaker] HA setup need to configure node transition if a resouce fails.

[emmanuel segura]

look this link
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/ch-advanced-resources.html#id1015383

Il giorno 18 aprile 2012 13:29, Manish Punjabi
<manishpunjabi21 at gmail.com>ha scritto:

> output of crm config show
>
> node kirchoff.pal.net \
>         attributes standby="off"
> node tesla.pal.net \
>         attributes standby="off"
> primitive res_Filesystem_2 ocf:heartbeat:Filesystem \
>         params device="/dev/drbd1" directory="/u01" fstype="ext3" \
>         operations $id="res_Filesystem_2-operations" \
>         op start interval="0" timeout="60" \
>         op stop interval="0" timeout="60" \
>         op monitor interval="20" timeout="40" start-delay="0" \
>         op notify interval="0" timeout="60" \
>         meta target-role="started" migration-threshold="1"
> allow-migrate="true" resource-stickiness="INFINITY" failure-timeou
> t="10"
> primitive res_Filesystem_3 ocf:heartbeat:Filesystem \
>         params device="/dev/drbd0" directory="/jboss" fstype="ext3" \
>         operations $id="res_Filesystem_3-operations" \
>         op start interval="0" timeout="60" \
>         op stop interval="0" timeout="60" \
>         op monitor interval="20" timeout="40" start-delay="0" \
>         op notify interval="0" timeout="60" \
>         meta target-role="started" migration-threshold="1"
> allow-migrate="true" resource-stickiness="INFINITY" failure-timeou
> t="10"
> primitive res_IPaddr2_1 ocf:heartbeat:IPaddr2 \
>         params ip="115.111.252.135" \
>         operations $id="res_IPaddr2_1-operations" \
>         op start interval="0" timeout="20" \
>         op stop interval="0" timeout="20" \
>         op monitor interval="10" timeout="20" start-delay="0" \
>         meta target-role="started" migration-threshold="1"
> allow-migrate="true" resource-stickiness="INFINITY" failure-timeou
> t="10"
> primitive res_MailTo_1 ocf:heartbeat:MailTo \
>         params email="sucheta.dudwadkar at gmail.com,
> manishpunjabi21 at gmail.com,nilesh.hiremath at tcs.com" subject="DRBD Message:
> System Generated. Please do not reply." \
>         operations $id="res_MailTo_1-operations" \
>         op start interval="0" timeout="10" \
>         op stop interval="0" timeout="10" \
>
>
> On Tue, Apr 17, 2012 at 6:52 PM, Manish Punjabi <manishpunjabi21 at gmail.com
> > wrote:
>
>> Dear All,
>>
>>  I have configured DRBD and pacemaker for highly available setup with 2
>> nodes. Each node has oracle and jboss resources along with ClusterIp
>> resource. I have used resource stickiness to infinity to make services run
>> on  a stable node. But also I need to make sure that if any one service
>> fails then the entire service must move on to other node. I have added
>> collocation and ordering to ensure all to run on a single node at a time.
>> When i fail one service like jboss it just restarts it back on same machine
>> . I have set resource threshold to 1. What other configuration should I
>>  make to enable entire service move to another node on a single service
>> failure.
>>
>>
>> Thanks and Regards
>> Manish
>>
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
>


-- 
esta es mi vida e me la vivo hasta que dios quiera
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120418/f1c580af/attachment.htm>