Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-02-02 Thread Afek, Ifat (Nokia - IL)
On 02/02/2017, 15:43, "gordon chung" wrote: > > On 02/02/17 06:30 AM, Afek, Ifat (Nokia - IL) wrote: > > I understand. So clearly the use case of Vitrage raising alarms in Aodh is > > not relevant at the moment. > > We will have to think if over and see how Panko fits in the

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-02-02 Thread gordon chung
On 02/02/17 06:30 AM, Afek, Ifat (Nokia - IL) wrote: > I understand. So clearly the use case of Vitrage raising alarms in Aodh is > not relevant at the moment. > We will have to think if over and see how Panko fits in the use case. if the use case is that you wanted to store history of Vitrage

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-02-02 Thread Afek, Ifat (Nokia - IL)
On 31/01/2017, 18:43, "gordon chung" wrote: > On 31/01/17 08:34 AM, Afek, Ifat (Nokia - IL) wrote: > > If you query Vitrage (or get a notification from Vitrage) and then you > > query Aodh, then Aodh will not return any additional information. But – if > > you query only Aodh,

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-31 Thread gordon chung
On 31/01/17 08:34 AM, Afek, Ifat (Nokia - IL) wrote: > If you query Vitrage (or get a notification from Vitrage) and then you query > Aodh, then Aodh will not return any additional information. But – if you > query only Aodh, you will be aware of the fact that the instances are at > risk.

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-31 Thread Afek, Ifat (Nokia - IL)
On 30/01/2017, 19:11, "gordon chung" wrote: > > On 29/01/17 08:52 AM, Afek, Ifat (Nokia - IL) wrote: > > > > Vitrage could be enhanced to become an alarm orchestrator. > > The question is – do you want Vitrage to be one? > > And how would you describe the role of an alarm

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-30 Thread gordon chung
On 29/01/17 08:52 AM, Afek, Ifat (Nokia - IL) wrote: > On 26/01/2017, 20:09, "Julien Danjou" wrote: > >> On Thu, Jan 26 2017, gordon chung wrote: >> >>> On 26/01/17 11:41 AM, Julien Danjou wrote: >> >>> and vitrage would be an alarm orchestrator? >> >> Yup, something like

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-29 Thread Afek, Ifat (Nokia - IL)
On 26/01/2017, 20:09, "Julien Danjou" wrote: > On Thu, Jan 26 2017, gordon chung wrote: > > > On 26/01/17 11:41 AM, Julien Danjou wrote: > > > and vitrage would be an alarm orchestrator? > > Yup, something like that. It could be the one driving Zabbix and > creating

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-26 Thread Julien Danjou
On Thu, Jan 26 2017, gordon chung wrote: > On 26/01/17 11:41 AM, Julien Danjou wrote: >> So here's another question then: why wouldn't there be a "zabbix" alarm >> type in Aodh that could be created by a user (or another program) and >> that would be triggered by Aodh when Zabbix does something?

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-26 Thread gordon chung
On 26/01/17 11:41 AM, Julien Danjou wrote: > So here's another question then: why wouldn't there be a "zabbix" alarm > type in Aodh that could be created by a user (or another program) and > that would be triggered by Aodh when Zabbix does something? > Which is something that is really like the

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-26 Thread Julien Danjou
On Thu, Jan 26 2017, Afek, Ifat (Nokia - IL) wrote: > I’ll try to answer your question from a user perspective. Thanks for your explanation, it helped me a lot to understand how you view things. :) > Suppose a bridge has a bond of two physical ports, and Zabbix detects a signal > loss in one

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-26 Thread Afek, Ifat (Nokia - IL)
On 25/01/2017, 17:12, "Julien Danjou" wrote: > On Wed, Jan 25 2017, Afek, Ifat (Nokia - IL) wrote: > > To circle back to the original point, the main question that I asked and > started this thread is: why, why Aodh should store Vitrage alarms? What > are the advantages,

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-25 Thread Julien Danjou
On Wed, Jan 25 2017, Afek, Ifat (Nokia - IL) wrote: > As we see it, alarms can be generated by different sources – Aodh, Vitrage, > Nagios, Zabbix, etc. I think "generated" is the wrong word here. Aodh does not generate any alarms: it allows users to create them. And then it evaluates them and

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-25 Thread gordon chung
On 25/01/17 08:39 AM, Afek, Ifat (Nokia - IL) wrote: > As we see it, alarms can be generated by different sources – Aodh, Vitrage, > Nagios, Zabbix, etc. Each source has its own expertise and internal > implementation. Nagios and Zabbix can raise alarms about the physical layer, > Aodh can

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-25 Thread Afek, Ifat (Nokia - IL)
Hi, Alarm history and a database are definitely important, but they are not the main issue here. As we see it, alarms can be generated by different sources – Aodh, Vitrage, Nagios, Zabbix, etc. Each source has its own expertise and internal implementation. Nagios and Zabbix can raise alarms

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-25 Thread Julien Danjou
On Tue, Jan 24 2017, gordon chung wrote: > you mean, keep alarm history in aodh and also in panko if needed? i'm ok > with that. Yeah, IIRC there's an expirer in Aodh for alarm history based on TTL – that's enough. That should probably be replaced with just a hard limit on the number of history

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-24 Thread gordon chung
On 24/01/17 03:05 PM, Julien Danjou wrote: > I think Aodh emits notifications when something happens so it can be in > Panko indeed. I don't think it'd be fair to force Panko to have (a > recent) history though. :) i'm going to add a work item (for anyone): allow multiple notification topics

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-24 Thread Julien Danjou
On Tue, Jan 24 2017, gordon chung wrote: > just curious, why doesn't vitrage send an event to aodh (on the error > topic) in this case rather than get nova to do it? if you created an > event alarm in aodh to check for vitrage error events could it solve the > use case? i don't know if we

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-24 Thread gordon chung
On 24/01/17 03:01 AM, Afek, Ifat (Nokia - IL) wrote: > We understood that Aodh aims to be OpenStack alarming service, which is much > more than an ‘engine of alarm evaluation’ (as you wrote in your comment in > gerrit). If I may describe another use case for generic alarms - of OPNFV >

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-24 Thread Julien Danjou
On Tue, Jan 24 2017, Afek, Ifat (Nokia - IL) wrote: > Vitrage, and I assume that other projects, needs an “Alarm Manager”. The role > of an Alarm Manager is to store all alarms in the system, keep their history, > notify on changes, etc. Vitrage does not declare itself as an Alarm Manager, >

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-24 Thread Afek, Ifat (Nokia - IL)
Hi Julien, Before I reply to everything you wrote, I would like to ask a question that seems to be the core issue here. On 24/01/2017, 12:58, "Julien Danjou" wrote: On Tue, Jan 24 2017, Afek, Ifat (Nokia - IL) wrote: > We understood that Aodh aims to be OpenStack

Re: [openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-24 Thread Julien Danjou
On Tue, Jan 24 2017, Afek, Ifat (Nokia - IL) wrote: Hi Ifat, > We understood that Aodh aims to be OpenStack alarming service, which is much > more than an ‘engine of alarm evaluation’ (as you wrote in your comment in > gerrit). Well, currently it's not really more than that. We've been to the

[openstack-dev] [aodh][vitrage] Aodh generic alarms

2017-01-24 Thread Afek, Ifat (Nokia - IL)
Hi Julien, I’m sending this mail regarding the generic alarm that Alexey Weyl from the Vitrage team is trying to implement in Aodh [1][2]. We understood that Aodh aims to be OpenStack alarming service, which is much more than an ‘engine of alarm evaluation’ (as you wrote in your comment in