[Pacemaker] Rule constraint monitoring interval

[Andrew Beekhof]

On 10/10/2013, at 3:22 AM, Sam Gardner <lwnexgen at gmail.com> wrote:

> As I understand it, there are two ways to monitor the status of a resource.
> 
> 1) Use the monitor action on the resource agent script - this is equivalent to polling the resource at every <monitor interval>
> 
> 2) Write a value into the cib, and create a constraint rule and scoring to handle failover based on the value of that attribute. This is what the ocf:heartbeat:ethmonitor resource agent does.

Two different purposes.

'2' is for monitoring resource1 (ethernet link) in order to decide what to do with resource2 (something else).

Pretty sure you still need to define a monitor for ocf:heartbeat:ethmonitor, thats what would be updating the value in the cib.

> 
> In the second case, what is the interval at which the cib value is monitored? Does the constraint rule just get checked on an event basis - ie, whenever the cib value changes, the rule is evaluated again)?

yes

> 
> Thanks,
> Sam
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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://bugs.clusterlabs.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20131016/4589d5cf/attachment-0003.sig>