2011/7/22 Dan Urist wrote: > I am in the process of trying to write an fping RA, based on the > pacemaker ping RA. My impetus for this is that I would like the RA to > return success as soon as any ping succeeds; the behavior of linux's > system ping as used in the standard ping RA is to run COUNT pings > within the given deadline and only after COUNT or the deadline return > success if any of the pings succeeded-- very inefficient. > > My question is this: the ping RA sets default values for > OCF_RESKEY_CRM_meta_timeout and OCF_RESKEY_CRM_meta_interval, and it > tests that OCF_RESKEY_CRM_meta_interval is an integer greater than 0. > These variables aren't used anywhere else within the RA, but these are > the same values in the "actions" section of the metadata for the monitor > timeout and interval. I can't find any documentation that these > variables serve as defaults for the monitor action in either the OCF > agent developer guide or the pacemaker docs, but this seems to be the > intent. Is this what they're there for?
I think so. The values in the "actions" section of the metadata for the monitor timeout and interval, are used as monitor operation's default values. OCF_RESKEY_CRM_meta_timeout and OCF_RESKEY_CRM_meta_interval are come from the monitor operation's actual values. Best Regards, Yingliang Yang _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
_______________________________________________ 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