On Tue, Jun 3, 2008 at 2:09 AM, Alex Strachan <[EMAIL PROTECTED]> wrote: > State1 > > ====== > > nodeA resourceA ------- resourceC > > nodeB resourceB > > > State2 > > ====== > > nodeA resourceA > > nodeB resourceB ------- resourceC > > > > Rule: ResourceC can only start AFTER (resourceA or resourceB), a preference > for resourceA is needed. > > > > > > Attempted config > > ================ > > <rsc_colocation id="colocation_resourceC_resourceA" from="resourceA" > to="resourceC" score="900000"/> > > <rsc_order id="order_resourceC_resourceA" from="resourceC" > to="resource_resourceA" action="start" type="after" symmetrical="false"/> > > <rsc_colocation id="colocation_resourceC_resourceB" from="resourceB" > to="resourceC" score="300000"/> > > <rsc_order id="order_resourceC_resourceB" from="resourceC" > to="resource_resourceB" action="start" type="after" symmetrical="false"/> > > Due to the two rsc_order's, when I put nodeB to standby - resourceC stops on > nodeA. If I remove the rsc_order for resourceB then resourceC is attempted > to start before resourceB which is not possible.
maybe if you set score="0" for both rsc_order constraints... but then you'll be toast if neither A nor B can start. nor will C be recovered if A or B is restarted. basically there is no way to perfectly express what you're after. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
