[ClusterLabs] active/passive resource config

Strahil Nikolov hunter86_bg at yahoo.com
Fri Oct 25 11:10:54 EDT 2019

 A resource group is a perfect candidate for a group and should work quite well.Keep in mind that:1. This systemd service must be disabled on both nodes as the cluster will controll it2. Test in advance that the systemd service can start on each node3. You can add run_arping=true for the IP resource in order to learn if there is an IP collision.4. You can also consider adding default resource stickiness.
What do you mean that the setup is not acting as expected?
Best Regards,Strahil Nikolov
    В петък, 25 октомври 2019 г., 09:03:37 ч. Гринуич+3, jyd <471204256 at qq.com> написа:  
 Hi:    I want to user pacemaker to mange a resource named A,i want A only started on one node,only when the node is down or A can not started in this node,the A resource will started on other nodes.And config a virtual ip resource for A,the virtual ip only started on the node which A is runnind.so how to config that?i trid like this but it didn't act as i expected.
------------------pcs resource create A systemd:myservice   op  start  interval=0s  timeout=20s   monitor  interval=10s  timeout=20s   stop  interval=0s timeout=20s meta migration-threshold=3  failure-timeout=60

pcs resource create vip ocf:heartbeat:IPaddr2 ip= cidr_netmask=24 op monitor interval=20s  meta resource-stickiness=100

pcs constraint colocation add vip A INFINITY

pcs constraint order A then vip
Manage your subscription:

ClusterLabs home: https://www.clusterlabs.org/  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20191025/c338a2e6/attachment.html>

More information about the Users mailing list