> > > > > > This is not optimal. Nothing prevents the resource, that can > > > fence node sv2837 > > > to run on host sv2837. You just say, that it should run on > > > node sv2836. > > > > > > Better would be something like > > > > > > crm configure location place-fencing-sv2837 -inf: sv2837 > > > > > > or the equivalent in pcs. > > > > > > Greetings, > > > > Hi Michael, > > > > I thought that the lines above will do that: > > > > pcs constraint location ipmi-fencing-sv2837 prefers > sv2836=INFINITY > > > > pcs constraint location ipmi-fencing-sv2836 prefers > sv2837=INFINITY > > > > Don't they? > > I don't know pcs in depth and I could not find any detailed > doc. So I stick > with crmsh. > > As far as I can judge your lines above your tell the cluster, > that the > resource, that can fence node sv2836, gets INF points if it > runs on node > sv2837. But what happens if node sv2837 is down? Nothing > prevents the resource > starting on the node that it should fence. So if one node is > down both fencing > resources will run on the remaining node. No very nice. > > I suggest to assign -INF points to the resource that can > fence node sv2836 if > it runs on node sv2836. So it will run on sv2837. If that node is not > available the resource cannot run. On the node (remaining) > node sv2836 only > the resource that can fence sv2837. > > For details see: http://clusterlabs.org/doc/crm_fencing.html > > Mit freundlichen Grüßen, > > Michael Schwartzkopff
Aaaah.... I see... thanks a lot for the explanation! br, christian _______________________________________________ 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
