[Pacemaker] "allow-migrate"
sinchb
sinchb at 163.com
Thu Mar 29 02:12:31 UTC 2012
I have a resource named myrsc .And it have the allow-migrate meta-attribute set to false.However,when I tried to migrate it ,I successed.Why it is?
Definition:
primitive myrsc ocf:heartbeat:IPaddr2 \
params ip="1.1.1.1" cidr_netmask="32" \
meta target-role="Started" allow-migrate="false" \
op monitor interval="10" timeout="120"
Command:
crm(live)resource# show myrsc
resource myrsc is running on: h10_147
crm(live)resource# migrate myrsc
WARNING: Creating rsc_location constraint 'cli-standby-myrsc' with a score of -INFINITY for resource myrsc on h10_147.
This will prevent myrsc from running on h10_147 until the constraint is removed using the 'crm_resource -U' command or manually with cibadmin
This will be the case even if h10_147 is the last node in the cluster
This message can be disabled with -Q
crm(live)resource# show myrsc
resource myrsc is running on: h10_148
As the output shown above ,when I tried to migrate myrsc , I successed,which is not expected and really make me confused.
I am looking forward to your reply.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120329/274fc6c6/attachment-0003.html>
More information about the Pacemaker
mailing list