Thanks.
I see. My nodes both have BMC to implement IPMI. But we don`t hope node
shoot itself. So in my case, "location" is necessary to prevent
fence_impilan runing on its shooting node.
On 05/14/2014 03:00 PM, Andrew Beekhof wrote:
On 12 May 2014, at 6:04 pm, david.miao <da...@shannon-data.com> wrote:
I install fence_ipmilan with the command: yum install fence-agents
My stonith configuration is as following:
node master
node slave
...
primitive stonith-master stonith:fence_ipmilan \
params ipaddr=192.168.1.36 login=root passwd=master pcmk_host_list=master
pcmk_host_check=static-list action=off \
op monitor interval=30s
primitive stonith-slave stonith:fence_ipmilan \
params ipaddr=192.168.1.37 login=root passwd=slave pcmk_host_list=slave
pcmk_host_check=static-list action=off delay=15s \
op monitor interval=30s
location stonith-master-mutex-master stonith-master -inf: master
location stonith-slave-mutex-slave stonith-slave -inf: slave
This can work, but my question is: Are the "location" above necessary?
No.
Can I use pcmk_host_list="some nodes" to control which nodes the fence_ipmilan
agent can run on?
Where it runs isn't so important. Particularly in a two node cluster (we'll
always try it from the node not being fenced first).
If can`t, what is the meaning of the pcmk_host_list. I have referenced to the
manual but I can`t understand.
Its a list of nodes the device can shoot/fence.
_______________________________________________
Pacemaker mailing list: Pacemaker@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
_______________________________________________
Pacemaker mailing list: Pacemaker@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
