On 2010-01-13T20:38:00, jaspal singla <[email protected]> wrote:
> group group_vz_1 vip_ipaddr2 filesystem1_Filesystem vz1_script \
> meta target-role="started"
> group group_vz_2 vip2_ipaddr2 filesystem2_Filesystem vz2_script \
> meta target-role="started"
> location location_master group_vz_1 700: node_master
> location location_node3 group_vz_2 600: node3
> location location_slave_1 group_vz_1 0: node_slave
> location location_slave_2 group_vz_2 0: node_slave
> colocation colocation_vz_test -inf: group_vz_1 group_vz_2
The anti-collocation rule you have is correct, and this should result in
the resources not being placed on the same node.
> property $id="cib-bootstrap-options" \
> dc-version="1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7" \
> cluster-infrastructure="Heartbeat" \
> stonith-enabled="false" \
> symmetric-cluster="false" \
> last-lrm-refresh="1263311374"
Disabling stonith is not a good idea if you're running shared storage.
> rsc_defaults $id="rsc_defaults-options"
You may want to enable resource-stickiness to avoid resources shuffling
around needlessly.
Regards,
Lars
--
Architect Storage/HA, OPS Engineering, Novell, Inc.
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
