Hi,
as far as I understand groups, the parameter ordered means, when set to yes,
that the resources in the group are started and stopped in the order that
they appear in the CIB. The collocated parameter means, that when set to
yes, all resources in a group run on the same cluster node.
I just created the following resource group:
<resources>
<group id="group_TEST">
<meta_attributes id="group_TEST_meta_attrs">
<attributes>
<nvpair id="group_TEST_metaattr_target_role" name="target_role"
value="started"/>
<nvpair id="group_TEST_metaattr_ordered" name="ordered"
value="false"/>
<nvpair id="group_TEST_metaattr_collocated" name="collocated"
value="true"/>
</attributes>
</meta_attributes>
<primitive id="D1" class="ocf" type="Dummy" provider="heartbeat">
<meta_attributes id="D1_meta_attrs">
<attributes>
<nvpair id="D1_metaattr_target_role" name="target_role"
value="stopped"/>
</attributes>
</meta_attributes>
</primitive>
<primitive id="D2" class="ocf" type="Dummy" provider="heartbeat">
<meta_attributes id="D2_meta_attrs">
<attributes>
<nvpair id="D2_metaattr_target_role" name="target_role"
value="started"/>
</attributes>
</meta_attributes>
</primitive>
<primitive id="D3" class="ocf" type="Dummy" provider="heartbeat"/>
</group>
</resources>
there ordered is set to false. I have the group running, and when I then
e.g. want to stop the resource D2, then D3 stops too. Only when I change
collocated to false, then D3 keeps running when I stop D2.
Seems to be not working as I understood it. Am I missing anything important
here, or maybe just a bug?
I'm on sles10sp1, using heartbeat 2.1.3.
cheers
Sebastian
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
