Hi,
You can find the meeting minutes of Vitrage meeting:
http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-20-09.00.html
Meeting log:
http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-20-09.00.log.html
See you next week,
Ifat.
Hi,
I added vitrage graph design, you can find it in:
https://github.com/openstack/vitrage/blob/master/doc/source/vitrage-graph-design.rst
Feel free to comment.
Thanks,
Ifat.
__
OpenStack Development Mailing List (not
Hi,
We will have Vitrage weekly meeting tomorrow, Wednesday at 9:00 UTC, on
#openstack-meeting-3 channel.
Agenda:
* Current status and progress from last week
* Review action items
* Next steps
* Open Discussion
You are welcome to join.
Thanks,
Ifat.
Hi,
You can find the meeting minutes of Vitrage meeting:
http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-13-09.00.html
Meeting log:
http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-13-09.00.log.html
See you next week,
Ifat.
Hi Pradeep,
> From: Pradeep Kilambi [mailto:pkila...@redhat.com]
> Sent: Thursday, January 07, 2016 9:15 PM
>
> > > alternatively, it was discussed that maybe adding a zaqar notifier
> > > would be useful. that way, aodh-notifier would send alarm to zaqar and
> > > you could configure it to
to, or something else?
[1] https://review.openstack.org/#/c/246727/
Thanks,
Ifat.
> -Original Message-
> From: Julien Danjou [mailto:jul...@danjou.info]
> Sent: Friday, January 08, 2016 11:42 AM
>
> On Thu, Jan 07 2016, AFEK, Ifat (Ifat) wrote:
>
> > We have two motivati
> -Original Message-
> From: gord chung [mailto:g...@live.ca]
> Sent: Wednesday, January 06, 2016 3:52 PM
>
> On 06/01/2016 8:11 AM, AFEK, Ifat (Ifat) wrote:
> > Hi,
> >
> > We would like to be notified once an alarm state is changed, so we
> prefer us
d by "alarm-history" API, may be
> you want to do aggregation on events data ?
>
> Thanks
> Liu sheng
>
> 在 2016/1/5 21:37, AFEK, Ifat (Ifat) 写道:
> >> -Original Message-
> >> From: gord chung [mailto:g...@live.ca]
> >> Sent: Friday, Dece
> -Original Message-
> From: gord chung [mailto:g...@live.ca]
> Sent: Friday, December 11, 2015 10:17 PM
>
> the original reason this was implemented i believe was to track alarm
> state changes as an event in ceilometer events. i still see this as a
> valid use case but it does duplicate
Hi,
The next two Vitrage meetings (this week and next week) are canceled.
We will meet again on Wednesday January 6 at 9:00 UTC, on #openstack-meeting-3
channel.
Thanks,
Ifat.
__
OpenStack Development Mailing List (not
> -Original Message-
> From: Ryota Mibu [mailto:r-m...@cq.jp.nec.com]
> Sent: Tuesday, December 08, 2015 11:17 AM
>
> Hi Ifat,
>
> In short, 'event' is generated in OpenStack, 'alarm' is defined by a
> user. 'event' is a container of data passed from other OpenStack
> services through
Hi,
In Vitrage[1] project we handle different kinds of resources, even ones
that are not managed by OpenStack. For example, we can get from nagios
information about an unreachable switch. I don't know in advance what
the different IDs would look like, since we have an open pluggable
Hi,
Minutes of today's Vitrage IRC meeting:
http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-12-16-09.00.html
See you next week,
Ifat.
__
OpenStack Development Mailing List (not for usage questions)
Hi,
Vitrage next weekly meeting will be tomorrow, Wednesday at 9:00 UTC, on
#openstack-meeting-3 channel.
Agenda:
* Current status and progress from last week
* Review action items
* Next steps
* Open Discussion
You are welcome to join.
Thanks,
Ifat.
Hi,
Reminder: Gerrit upgrade is scheduled for tomorrow at 17:00 UTC.
Ifat.
-Original Message-
From: Spencer Krum [mailto:n...@spencerkrum.com]
Sent: Monday, December 14, 2015 9:53 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Gerrit Upgrade 12/16
This is a
Hi Ryota,
> -Original Message-
> From: Ryota Mibu [mailto:r-m...@cq.jp.nec.com]
> Sent: Tuesday, December 08, 2015 11:17 AM
>
> In short, 'event' is generated in OpenStack, 'alarm' is defined by a
> user. 'event' is a container of data passed from other OpenStack
> services through
Hi,
Our last Vitrage meeting was not recorded properly due to an update of
OpenStack bot that was performed in the middle of our meeting. Anyway, you can
still view the meeting log in
http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-12-09-09.00.log.txt
Ifat.
Hi,
Vitrage next weekly meeting will be tomorrow, Wednesday at 9:00 UTC, on
#openstack-meeting-3 channel.
Agenda:
* Current status and progress from last week
* Review action items
* Next steps
* Open Discussion
You are welcome to join.
Thanks,
Ifat.
> -Original Message-
> From: Julien Danjou [mailto:jul...@danjou.info]
> Sent: Monday, December 07, 2015 12:00 PM
>
> I find it odd to have UI use cases first, as their terribly large for a
> MVP. Unless Vitrage already exists and you have all the code figured
> out. :)
We have most of it
hat
> Monasca creates be a source for the Vitrage Synchronizer?
>
> Regards --Roland
>
>
> On 11/17/15, 3:02 AM, "AFEK, Ifat (Ifat)" <ifat.afek@alcatel-
> lucent.com>
> wrote:
>
> >Hi Monasca developers,
> >
> >As you might hav
Hi Julien,
> -Original Message-
> From: Julien Danjou [mailto:jul...@danjou.info]
> Sent: Thursday, December 03, 2015 4:27 PM
>
> I think that I would be more interested by connecting Nagios to
> Ceilometer/Gnocchi/Aodh with maybe the long-term goal of replacing it
> by that stack, which
Hi Ryota,
> -Original Message-
> From: Ryota Mibu [mailto:r-m...@cq.jp.nec.com]
> Sent: Friday, December 04, 2015 9:42 AM
>
> > The next step can happen if and when Aodh supports alarm templates.
> > If Vitrage can handle about 30 alarm types, and there are 100
> > instances, we don't
Hi Julien,
> From: Julien Danjou [mailto:jul...@danjou.info]
> Sent: Thursday, December 03, 2015 10:53 AM
>
> On Thu, Dec 03 2015, AFEK, Ifat (Ifat) wrote:
>
> > Another question is our need to get alarms from other sources, like
> > Nagios, zabbix, ganglia, etc. We
Hi Ryota,
> From: Ryota Mibu [mailto:r-m...@cq.jp.nec.com]
> >
> > Let me see if I got this right: are you suggesting that we create
> > on-the-fly alarm definitions with no alarm_actions, for every deduced
> alarm that we want to raise? And this will spare us the extra alarm
> evaluation in
Hi,
In Vitrage[3] project, we would like to be notified on every alarm that is
triggered, and respond immediately (e.g. by generating RCA insights, or by
triggering new alarms on other resources). We are now in the process of
designing our integration with AODH.
If I understood you correctly,
Hi Julien,
Please see our questions below.
Ifat and Elisha.
> -Original Message-
> From: Julien Danjou [mailto:jul...@danjou.info]
>
> On Wed, Dec 02 2015, ROSENSWEIG, ELISHA (ELISHA) wrote:
> > Regarding the second point: Say we have 30 different types of alarms
> > we might want to
Hi Ryota,
Thanks for your response, please see my comments below.
Ifat.
> -Original Message-
> From: Ryota Mibu [mailto:r-m...@cq.jp.nec.com]
>
> Hi,
>
>
> Sorry for my late response...
>
> It seems like a fundamental question whether we should have rich
> function or intelligence
> -Original Message-
> From: Julien Danjou [mailto:jul...@danjou.info]
>
> On Wed, Dec 02 2015, AFEK, Ifat (Ifat) wrote:
>
> > Can this be supported without defining an alarm for every VM
> separately?
>
> No, it's not possible. You'd have to create the ala
Hi,
Here are the minutes of today's meeting:
http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-12-02-09.01.html
Meeting log:
http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-12-02-09.01.log.html
See you next time,
Ifat.
AODH focus on
metric-related alarms?
Thanks,
Ifat.
> -Original Message-
> From: AFEK, Ifat (Ifat) [mailto:ifat.a...@alcatel-lucent.com]
> Sent: Monday, November 30, 2015 2:47 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [
Hi,
Vitrage next weekly meeting will be tomorrow, Wednesday at 9:00 UTC, on
#openstack-meeting-3 channel.
Agenda:
* Current status and progress from last week
* Review action items
* Next steps
* Open Discussion
You are welcome to join.
Thanks,
Ifat.
Hi,
A few days ago I sent you this email (see below). Resending in case you didn't
see it.
If you could get back to me soon it would be most appreciated, as we are quite
blocked with our AODH integration right now.
Thanks,
Ifat.
-Original Message-
From: AFEK, Ifat (Ifat
h][vitrage] Raising custom
> alarms in AODH
>
>
>
> On 23/11/2015 11:14 AM, AFEK, Ifat (Ifat) wrote:
> > I guess I would like to do both: create a new alarm definition, then
> > trigger it (call alarm_actions), and possibly later on set its state
> > back to OK (c
ists.openstack.org
> Subject: Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising
> custom alarms in AODH
>
>
>
> On 23/11/2015 11:14 AM, AFEK, Ifat (Ifat) wrote:
> > I guess I would like to do both: create a new alarm definition, then
> > trigger it (call
Hi,
Vitrage weekly meeting will be tomorrow, Wednesday at 9:00 UTC, on
#openstack-meeting-3 channel.
Agenda:
* Current status and progress from last week
* Review action items
* Next steps
* Open Discussion
You are welcome to join.
Vitrage meetings page:
Hi,
We have a couple of questions regarding AODH alarms.
In Vitrage[1] project we have two use cases that involve Ceilometer:
1. Import Ceilometer alarms, as well as alarms and resources from other sources
(Nagios, Zabbix, Nova, Heat, etc.), and produce RCA insights about the
connection
ms in AODH
>
> hi Ifat,
>
> i added some questions below.
>
> On 23/11/2015 7:16 AM, AFEK, Ifat (Ifat) wrote:
> > Hi,
> >
> > We have a couple of questions regarding AODH alarms.
> >
> > In Vitrage[1] project we have two use cases that involve
mation
from Neutron. We will probably add these source plug-ins in stages. Right now
they are all referred to in the synchronizer blueprint, but this design is
still in progress. In general, the more input Vitrage gets, the more valuable
alarm insights it can produce.
Obviously, Vitrage can benefit a l
Hi Ceilometer/AODH developers,
As you might have heard in Mitaka Summit, we have started a new project named
Vitrage[1]. We would like it to be the Openstack RCA (Root Cause Analysis)
Engine for organizing, analyzing and expanding OpenStack alarms & events,
yielding insights regarding the root
Hi,
Vitrage next weekly meeting will be tomorrow, Wednesday at 9:00 UTC, on
#openstack-meeting-3 channel.
Agenda:
* Current status and progress from last week
* Review action items
* Next steps
* Open Discussion
You are welcome to join.
Thanks,
Ifat.
Hi Monasca developers,
As you might have heard in Mitaka Summit, we have started a new project named
Vitrage[1]. We would like it to be the Openstack RCA (Root Cause Analysis)
Engine for organizing, analyzing and expanding OpenStack alarms & events,
yielding insights regarding the root cause
Hi,
Vitrage next weekly meeting will be tomorrow, Wednesday at 9:00 UTC, on
#openstack-meeting-3 channel.
A link to the agenda: https://wiki.openstack.org/wiki/Meetings/Vitrage
Ifat.
__
OpenStack Development Mailing List
42 matches
Mail list logo
