Hi Rodrigo,
On 27/12/2007, at 1:00 AM, Rodrigo Pereira wrote:
Hi,
I have a running cluster, with a couple of Xen VM's on top of DRBD.
I have colocation constraints for each Xen VM resource so they only
start
where the DRBD fs is mounted. Something like:
<rsc_colocation id="vm1_on_fs0" from="vm1" to="fs0" score="INFINITY"/>
I created another Xen VM, and tried to add it to the cluster. I have
all
resources on one xml file and all constraints on another. I then use
cib_admin to update each (i update constraints before resources).
I thought it would respect the colocation constraint, but what i've
found is
that this resulted on this new VM trying to start on the second (DRBD
secondary) node, not the one where fs0 is mounted. So it fails
startup and
stays unmanaged.
I have -very- limited knowledge on CRM-mode heartbeat but heres a
total shot in the dark:
When you apply the constrains the service doesn't exist yet so its
either ignoring it and not adding it when you add the service or its
just not adding the constraint at all.
Thus I would recommend first adding the service in a stopped state,
adding the co-location constraint and then starting it.
Regards,
Trent
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
