[ClusterLabs] How to make a node persistent active in pacemaker-corosync?

Takehiro Matsushima takehiro.dreamizm at gmail.com
Mon Dec 11 21:13:25 EST 2017


If you want to be active resource on node0 prior to node1, try using
#uname in "location" like this: (example in crmsh)
location some-resource-location some-resource \
  rule 100: #uname eq node0 \
  rule 50: #uname ne node0
It allows to be active "some-resource" resource on node0 when it is available.


2017-12-10 20:10 GMT+09:00 Ricardo Cristian Ramirez
<r.cristian.ramirez at gmail.com>:
> Hi all,
> I have an active-passive pacemaker-corosync configuration.
> When a node is powered up before the other one, it becomes active, and the
> node, which is powered up second, becomes passive.
> (For a node, being active means that to run resources on itself.)
> What I want is that to have a node which is persistenly active while it is
> powered up.
> For example, say we want node0 as persistent active node, and node1 as
> passive node.
> Scenario:
>     Power up node1 (node1 is active)
>     Power up node0 (node0 is active, node1 is passive)
> What is the correct way of doing this?
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://lists.clusterlabs.org/mailman/listinfo/users
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

More information about the Users mailing list