> > Colocation constraints may take a "node-attribute" parameter, that > basically means, "Put this resource on a node of the same class as the > one running resource X". > > In this case, you might set a "group" node attribute on all nodes, to > "1" on the three primary nodes and "2" on the three failover nodes. > Pick one resource as your base resource that everything else should go > along with. Configure colocation constraints for all the other > resources with that one, using "node-attribute=group". That means that > all the other resources must be one a node with the same "group" > attribute value as the node that the base resource is running on. > > "node-attribute" defaults to "#uname" (node name), this giving the > usual behavior of colocation constraints: put the resource only on a > node with the same name, i.e. the same node. > > The remaining question is, how do you want the base resource to fail > over? If the base resource can fail over to any other node, whether in > the same group or not, then you're done. If the base resource can only > run on one node in each group, ban it from the other nodes using > -INFINITY location constraints. If the base resource should only fail > over to the opposite group, that's trickier, but something roughly > similar would be to prefer one node in each group with an equal > positive score location constraint, and migration-threshold=1.
I just want to let you know that this worked like a charm. Again, thank you very much. Best regards, Alberto Mijares _______________________________________________ Users mailing list: Users@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