Harakiri wrote:
Hello,
i've got some ressources configured to be started only at one node in a
cluster. The problem is, that i cant force that all ressources are started on
the same node. I have a virtual ip ressource which points to one active node,
and then i have a sync script which may be running on another node.
Is it possible to force heartbeat to start all ressources on the same node and
not mix them between different nodes? And when this node goes down, they should
all start on another single node.
As suggested in another reply, look into colocation constraints. If you
only use primitive resources (no clones or master/slave resources), you
could also use a group instead of single resources. In fact, groups are
just a syntax shortcut for colocation constraints between all resources
within that group, but that happens in the background.
Regards
Dominik
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
