Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

ers@clusterlabs.org> > Cc: > Date: 2016/5/14, Sat 00:51 > Subject: Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts > > On 05/13/2016 04:59 PM, renayama19661...@ybb.ne.jp wrote: >> i Klaus, >> >> After all we want transmission order. >> I think that I

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

--- Original Message - >> From: "renayama19661...@ybb.ne.jp" <renayama19661...@ybb.ne.jp> >> To: "kwenn...@redhat.com" <kwenn...@redhat.com>; "users@clusterlabs.org" >> <users@clusterlabs.org>; Cluster Labs - All topics related t

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

gt; - Original Message - >> From: Klaus Wenninger <kwenn...@redhat.com> >> To: users@clusterlabs.org >> Cc: >> Date: 2016/5/11, Wed 14:13 >> Subject: Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts >> >> On 05/10/2016 11:19 PM, rena

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

s - All topics related to open-source > clustering welcomed <users@clusterlabs.org> > Cc: > Date: 2016/4/28, Thu 22:43 > Subject: Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts > > Hi Klaus, > > Because the script is performed the effectiveness of in async, I

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

Preparing the updated Pacemaker-Explained-section I read through this again. I guess most points where this differs from the actual implementation - currently in the repo - were discussed already but where I remember them I'll insert them here anyway to have them in one place. Reason why I wrote

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

On 04/25/2016 07:28 AM, Lars Ellenberg wrote: > 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

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

On 04/22/2016 05:55 PM, Adam Spiers wrote: > Ken Gaillot wrote: >> On 04/21/2016 06:09 PM, Adam Spiers wrote: >>> Ken Gaillot wrote: Hello everybody, The release cycle for 1.1.15 will be started soon (hopefully tomorrow)! The

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

On 04/28/2016 10:24 AM, Lars Marowsky-Bree wrote: > On 2016-04-27T12:10:10, Klaus Wenninger wrote: > >>> Having things in ARGV[] is always risky due to them being exposed more >>> easily via ps. Environment variables or stdin appear better. >> What made you assume the

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

On 2016-04-27T12:10:10, Klaus Wenninger wrote: > > Having things in ARGV[] is always risky due to them being exposed more > > easily via ps. Environment variables or stdin appear better. > What made you assume the recipient is being passed as argument? > > The environment

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

/28, Thu 03:14 > Subject: Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts > > On 04/27/2016 04:19 PM, renayama19661...@ybb.ne.jp wrote: >> Hi All, >> >> We have a request for a new SNMP function. >> >> >> The order of traps is not right. &g

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

Hi All, We have a request for a new SNMP function. The order of traps is not right. The turn of the trap is not sometimes followed. This is because the handling of notice carries out "path" in async. I think that it is necessary to wait for completion of the practice at "path" unit of

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

Klaus Wenninger writes: >> >> alert alert-1 /srv/pacemaker/pcmk_alert_sample.sh \ >> to /var/log/cluster-alerts.log > Are (and if yes how) you planning to handle multiple recipients? Yes, just put multiple "to" statements after each other: alert alert-1

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

On 04/27/2016 12:12 PM, Kristoffer Grönlund wrote: > Ken Gaillot writes: > >> 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,

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

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

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

On 2016-04-21T12:50:43, Ken Gaillot wrote: Hi all, awesome to see such a cool new feature land! I do have some questions/feedback though. > The alerts section can have any number of alerts, which look like: > > path="/srv/pacemaker/pcmk_alert_sample.sh"> >

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

Klaus Wenninger writes: > On 04/25/2016 08:03 AM, Kristoffer Grönlund wrote: >>> In the current implementation, meta-attributes and instance attributes >>> may also be specified within the block, in which case they >>> override any values specified in the block when sent

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

On 04/25/2016 08:03 AM, Kristoffer Grönlund wrote: > Ken Gaillot writes: > >> 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

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

Ken Gaillot writes: > 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

Re: [ClusterLabs] Coming in 1.1.15: Event-driven alerts

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