On Fri, Oct 25, 2019 at 9:03 AM jyd <471204...@qq.com> wrote: > > 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. >
And what exactly did not work as 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=192.168.2.87 cidr_netmask=24 > op monitor interval=20s meta resource-stickiness=100 > > pcs constraint colocation add vip A INFINITY > > pcs constraint order A then vip You did not add any location constraints so pacemaker is free to chose any node if this is what you mean under "not as expected". _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
