Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior

2018-02-22 Thread Afek, Ifat (Nokia - IL/Kfar Sava)
, 21 February 2018 at 19:11 To: "Afek, Ifat (Nokia - IL/Kfar Sava)" , "OpenStack Development Mailing List (not for usage questions)" Cc: Ciprian Barbu Subject: RE: [openstack-dev] [vitrage] Vitrage alarm processing behavior Hi Ifat, Link to cuted log version https://hasteb

Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior

2018-02-21 Thread Afek, Ifat (Nokia - IL/Kfar Sava)
tachment removed] Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior Hi Ifat, Sorry for the late reply. To answer your questions I started as an example from the doctor datasource (or a porting of it for the 1.3.0 version of vitrage) but will call it something different so no

Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior

2018-02-21 Thread Paul Vaduva
Sorry forgot to add you. From: Paul Vaduva Sent: Wednesday, February 21, 2018 4:31 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Ciprian Barbu Subject: RE: [openstack-dev] [vitrage] Vitrage alarm processing behavior I attached also the driver.py that I am using

Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior

2018-02-21 Thread Paul Vaduva
om: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com] Sent: Wednesday, February 7, 2018 1:24 PM To: OpenStack Development Mailing List (not for usage questions) mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior Hi

Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior

2018-02-21 Thread Paul Vaduva
From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com] Sent: Wednesday, February 7, 2018 7:16 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Ciprian Barbu Subject: Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior Hi Paul, I’m glad th

Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior

2018-02-07 Thread Afek, Ifat (Nokia - IL/Kfar Sava)
: "OpenStack Development Mailing List (not for usage questions)" Date: Wednesday, 7 February 2018 at 15:50 To: "OpenStack Development Mailing List (not for usage questions)" Cc: Ciprian Barbu Subject: Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior Hi Ifat, Yes I’

Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior

2018-02-07 Thread Paul Vaduva
t: Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior Hi Paul, It sounds like a bug. Alarms created by a datasource are not supposed to be deleted later on. It might be a bug that was fixed in Queens [1]. I’m not sure which Vitrage version you are actually using. I failed to f

Re: [openstack-dev] [vitrage] Vitrage alarm processing behavior

2018-02-07 Thread Afek, Ifat (Nokia - IL/Kfar Sava)
Stack Development Mailing List (not for usage questions)" Date: Wednesday, 7 February 2018 at 11:58 To: "openstack-dev@lists.openstack.org" Subject: [openstack-dev] [vitrage] Vitrage alarm processing behavior Hi Vitrage developers, I have a question about vitrage innerworkings, I port

[openstack-dev] [vitrage] Vitrage alarm processing behavior

2018-02-07 Thread Paul Vaduva
Hi Vitrage developers, I have a question about vitrage innerworkings, I ported doctor datasource from master branch to an earlier version of vitrage (1.3.1). I noticed some behavior I am wondering if it's ok or it is bug of some sort. Here it is: 1. I am sending some event for rasing an alarm to