On 3/25/2011 at 08:38 AM, Alan Jones <falanclus...@gmail.com> wrote:
> I'm not asking about the behavior of the agent, but the status
> reported by pacemaker.
> An RA can correctly conform to the OCF specification and also take
> significant time for the start to complete.
> During that time pacemaker reports the resource state as 'Started'.
> How can I get access to an internal state in pacemaker that can
> distinguish between 'start in progress' and 'start completed'?
> Alan
Try this:
# crm configure op_defaults record-pending=true
Then this:
# crm resource start my-slow-resource
Then this:
# crm_resource --resource my-slow-resource -O
my-slow-resource (ocf::heartbeat:Delay) Started :
my-slow-resource_start_0 (node=node-0, call=-1, rc=14): pending
Then again, later:
# crm_resource --resource my-slow-resource -O
my-slow-resource (ocf::heartbeat:Delay) Started :
my-slow-resource_start_0 (node=node-0, call=86, rc=0): complete
Regards,
Tim
--
Tim Serong <tser...@novell.com>
Senior Clustering Engineer, OPS Engineering, Novell Inc.
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
