[ClusterLabs] Coming in 1.1.15: Event-driven alerts

Lars Ellenberg lars.ellenberg at linbit.com
Mon Apr 25 08:28:51 EDT 2016

On Thu, Apr 21, 2016 at 12:50:43PM -0500, Ken Gaillot wrote:
> Hello everybody,
> The release cycle for 1.1.15 will be started soon (hopefully tomorrow)!
> The most prominent feature will be Klaus Wenninger's new implementation
> of event-driven alerts -- the ability to call scripts whenever
> interesting events occur (nodes joining/leaving, resources
> starting/stopping, etc.).

What exactly is "etc." here?
What is the comprehensive list
of which "events" will trigger "alerts"?

My guess would be
 DC election/change
   which does not necessarily imply membership change
 change in membership
   which includes change in quorum
 fencing events
   (even failed fencing?)
 resource start/stop/promote/demote
  (probably) monitor failure?
   maybe only if some fail-count changes to/from infinity?
   or above a certain threshold?

 change of maintenance-mode?
 node standby/online (maybe)?
 maybe "resource cannot be run anywhere"?

would it be useful to pass in the "transaction ID"
or other pointer to the recorded cib input at the time
the "alert" was triggered?

can an alert "observer" (alert script) "register"
for only a subset of the "alerts"?

if so, can this filter be per alert script,
or per "recipient", or both?



More information about the Users mailing list