On Dec 11, 2007, at 1:24 PM, Dejan Muhamedagic wrote:
Hi,
On Tue, Dec 11, 2007 at 11:01:34AM +0100, Andrew Beekhof wrote:
On Dec 11, 2007, at 10:55 AM, matilda matilda wrote:
Dejan Muhamedagic <[EMAIL PROTECTED]> 11.12.2007 10:02 >>>
Hi Dejan,
You can also try crmadmin -S DC_NODE in a loop until it reports
the IDLE state, then check whichever resource you want.
but this is not an atomic operation. You have a gap between
"ohh, now the cluster seems to be idle" and checking if
the ressource is up. Am I wrong?
true. the only way to be sure is to do something like what the TE
does...
connect to the CIB, subscribe to updates and look for a successful
start
action for your resource(s)
Isn't it that the DC goes idle once the tengine finished with the
transition?
nod - but that doesn't necessarily imply that the cluster was able/
allowed/inclined to move the resource to a new node
one day i should probably write a tool for that
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
