Re: [openstack-dev] [vitrage] input erroneous `vitrage_id` in `vitrage rca show`API or `vitrage topology show` API

bug about it. Thanks, Ifat. From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Wednesday, May 25, 2016 9:24 AM To: Weyl, Alexey (Nokia - IL); Afek, Ifat (Nokia - IL); Rosensweig, Elisha (Nokia - IL); Shamir, Ohad (Nokia - IL) Subject: input erroneous `vitrage_id` in `vitrage rc

[openstack-dev] [vitrage] Vitrage meeting on June 22 - SKIPPED

Hi, Vitrage weekly meeting on June 22 will be skipped due to OPNFV summit. We will meet again on June 29. Thanks, Ifat. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [vitrage] vitrage - how much links model in API is permanent?

Hi Eylon, This dictionary is created by NetworkX, and is not about to be changed. You can definitely rely on this API to be permanent. And we should make sure we have a tempest test for verifying it. Best regards, Ifat. > -Original Message- > From: Malin, Eylon (Nokia - IL)

Re: [openstack-dev] [vitrage] input erroneous `vitrage_id` in `vitrage rca show`API or `vitrage topology show` API

, Ifat (Nokia - IL) <ifat.a...@nokia.com<mailto:ifat.a...@nokia.com>> wrote: Hi dwj, I’m passing the question (and answer) to openstack mailing list. You are right. In case of an invalid vitrage id, we should not return HTTP 404 error. I think the correct behavior would be to return

[openstack-dev] [vitrage] multi-tenancy in Vitrage

Hi, During the discussion about accepting vitrage into the big tent[1], there was a concern raised by a few people regarding whether Vitrage is suitable for a public cloud. They were bothered that allowing each user to see the entire cloud topology is not suitable in such environments. It is

[openstack-dev] [vitrage] Vitrage is now an official OpenStack project

Hi, Great news - Vitrage (OpenStack RCA service) was accepted into the big tent yesterday, in the TC IRC meeting[1]. Thanks to everyone who participated in this huge effort of creating a whole project from scratch in a little more than 6 months. Now, with the wind in our sails, we invite

[openstack-dev] [vitrage][aodh] Notifications about aodh alarm state changes

Hi Julien, Gordon, I understood that during Aodh-Vitrage design session in Austin, you had a discussion about Vitrage need for notifications about Aodh alarm state changes. Did you have a chance to think about it since, and to check how this can be done? Thanks, Ifat.

[openstack-dev] [vitrage] Next vitrage meeting

Hi, Vitrage next weekly meeting will be tomorrow, Wednesday at 9:00 UTC, on #openstack-meeting-3 channel. Agenda: * Current status * Review action items * Next steps * Open Discussion You are welcome to join. Thanks, Ifat.

[openstack-dev] [vitrage] Vitrage meeting minutes

Hi, You can find the meeting minutes of Vitrage meeting: http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-02-03-09.00.html Meeting log: http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-02-03-09.00.log.html See you next week, Ifat.

[openstack-dev] [vitrage] Vitrage meeting tomorrow

Hi, We will have Vitrage weekly meeting tomorrow, Wednesday at 9:00 UTC, on #openstack-meeting-3 channel. Agenda: * Current status * Review action items * Next steps * Open Discussion You are welcome to join. Thanks, Ifat.

[openstack-dev] [vitrage] Vitrage meeting tomorrow

Hi, We will have Vitrage weekly meeting tomorrow, Wednesday at 9:00 UTC, on #openstack-meeting-3 channel. Agenda: * Current status and progress * Review action items * Next steps * Open Discussion You are welcome to join. Thanks, Ifat.

[openstack-dev] [vitrage] Vitrage meeting minutes

Hi, You can find the meeting minutes of Vitrage meeting: http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-27-09.00.html Meeting log: http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-01-27-09.00.log.html See you next week, Ifat.

[openstack-dev] [vitrage] Vitrage meeting tomorrow

Hi, We will have Vitrage weekly meeting tomorrow, Wednesday at 9:00 UTC, on #openstack-meeting-3 channel. Agenda: * Current status and progress * Review action items * Next steps * Open Discussion You are welcome to join. Thanks, Ifat.

[openstack-dev] [vitrage] Vitrage meeting minutes

Hi, You can find the meeting minutes of Vitrage meeting: http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-02-17-09.00.html Meeting log: http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-02-17-09.00.log.html See you next week, Ifat.

Re: [openstack-dev] [vitrage] vitrage weekly meeting today

. > -Original Message- > From: EXT Afek, Ifat (Nokia - IL) [mailto:ifat.a...@nokia.com] > Sent: Wednesday, April 13, 2016 11:10 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: [openstack-dev] [vitrage] vitrage weekly meeting today &g

[openstack-dev] [vitrage] vitrage weekly meeting today

Hi, Due to daylight saving time issues - Vitrage meeting today will be at 9:00 UTC, which might be an hour later than usual. Ifat. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [vitrage] Austin preparation

Hi all, Here are the tasks that we should finish for the Austin summit, with the current owners: - List of default Templates + testing - danoffek - Description support in Templates - ifat_afek / (or lhartal?) - Installation - First Steps Guide - elisha_r - Aodh – Installation requirements

Re: [openstack-dev] [Vitrage] putting overlapping-templates-basic-support on the back-burner

> -Original Message- > From: Rosensweig, Elisha (Nokia - IL) > [mailto:elisha.rosensw...@nokia.com] > > Hi All, > > Since > * the overlapping templates BP > (https://blueprints.launchpad.net/vitrage/+spec/overlapping-templates- > basic-support) is a large one, which deserves a lot of

Re: [openstack-dev] [vitrage] Synchronizer - explanation and name refactoring

Great, I think it is much more clear now. I also think we should rename SyncMode and SyncType, these names are confusing. > -Original Message- > From: EXT Har-Tal, Liat (Nokia - IL) [mailto:liat.har-...@nokia.com] > Sent: Monday, April 11, 2016 9:44 AM > To:

[openstack-dev] [vitrage] vitrage topology show

Hi, vitrage topology show has a different behavior for a tree and a graph. In case it is called with no query: * For a tree it returns the node, zone, host and instances * For a graph it returns everything I don't think that the selected topology representation should affect the type of

[openstack-dev] [vitrage] Vitrage demo

Hi, I uploaded a new Vitrage demo, which shows deduced alarms, deduced states and root cause analysis: https://www.youtube.com/watch?v=vqlOKTmYR4c Let me know if you have any comments or questions. Thanks, Ifat. __

[openstack-dev] [vitrage] Vitrage meeting on Apr 27 - SKIPPED

Hi, Vitrage weekly meeting on April 27 will be skipped. We will meet again on the week of May 1. Thanks, Ifat. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [vitrage] Vitrage IRC meetings - notice the change of time

Hi, Reminder: Vitrage weekly meeting time and channel were be changed to: Wednesday at 8:00 UTC, #openstack-meeting-4 See you on Wednesday, Ifat. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [vitrage] Normalized Resource State

> -Original Message- > From: EXT Malin, Eylon (Nokia - IL) [mailto:eylon.ma...@nokia.com] > Sent: Monday, May 16, 2016 6:09 PM > > Hi all, > > Aggregated_state can has only values from NormalizedResourceState which > is constant enum. > Currently the NormalizedResourceState has these

Re: [openstack-dev] [vitrage] Normalized Resource State

gt; > -Original Message----- > > From: Afek, Ifat (Nokia - IL) [mailto:ifat.a...@nokia.com] > > Sent: Monday, May 16, 2016 6:29 PM > > > > > -Original Message- > > > From: EXT Malin, Eylon (Nokia - IL) [mailto:eylon.ma...@noki

Re: [openstack-dev] [vitrage] Design discussion for overlapping templates support & new section in Vitrage wiki

Hi Elisha, Great design :-) I added a few comments in the etherpad. Ifat. -Original Message- From: EXT Rosensweig, Elisha (Nokia - IL) [mailto:elisha.rosensw...@nokia.com] Sent: Wednesday, May 11, 2016 9:56 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [vitrage]

[openstack-dev] [vitrage] Vitrage meeting - Newton design

Hi, We started Vitrage Newton planning on the IRC meeting today. You can find the minutes here: http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-05-04-09.00.html Meeting log: http://eavesdrop.openstack.org/meetings/vitrage/2016/vitrage.2016-05-04-09.00.log.html You are

[openstack-dev] [vitrage] Vitrage meeting on May 4 - Newton design

Hi, Next Vitrage weekly meeting will be held on the coming Wednesday, May 4, at 9:00 UTC. Agenda: * Ohad and alexey_weyl will update on Austin Summit and their presentations[1][2] * We will start working on Vitrage Newton plan. I opened an etherpad for this purpose[3], please use it to add

Re: [openstack-dev] [vitrage] the section of vitrage.transformers in setup.cfg is not used

Hi, You are right, it is an old configuration that we should delete. Thanks for reporting this bug, and you are welcome to contact us again with any questions or suggestions you might have :) Best regards, Ifat. From: EXT dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Monday,

[openstack-dev] [vitrage] Vitrage IRC meetings - notice the change of time

Hi, Vitrage meeting this week will be SKIPPED, as many Vitrage developers won't be able to attend. Starting from next week, the meeting time and channel will be changed to: Wednesday at 8:00 UTC, #openstack-meeting-4 See you next Week, Ifat.

[openstack-dev] [vitrage] Vitrage weekly meeting

Hi, Vitrage weekly meeting will be held tomorrow at 9:00 UTC. Notice the daylight saving time issues - it might be one hour late. We will have a short meeting focused on the preparations for Austin Summit. Thanks, Ifat.

[openstack-dev] [vitrage] Vitrage meeting on May 25 - SKIPPED

Hi, Vitrage weekly meeting on May 25 will be skipped, as many Vitrage developers won't be able to attend. We will meet next week as usual. Thanks, Ifat. __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [horizon][vitrage] Midcycle Summary

> -Original Message- > From: Matthias Runge [mailto:mru...@redhat.com] > Sent: Friday, July 22, 2016 9:53 AM > > Did you also talk about deprecating of ceilometer based metering > dashboard? > > IIRC, we all agreed at the last summit, this doesn't really work for > large deployments and

Re: [openstack-dev] [devstack][vitrage] some compress error when deploy OS

Hi, I’m glad that you found a workaround. Someone from vitrage-dashboard team should look at the specific error and tell you what is the best solution. Best Regards, Ifat. From: Yujun Zhang [mailto:zhangyujun+...@gmail.com] Sent: Wednesday, July 27, 2016 9:11 AM To: OpenStack Development

Re: [openstack-dev] [telemetry] [vitrage] Mascot

> -Original Message- > From: Ildikó Váncsa [mailto:ildiko.van...@ericsson.com] > Sent: Thursday, July 21, 2016 9:36 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [telemetry] Mascot > > I had the Meerkat [1] in mind as Telemetry has a

[openstack-dev] [vitrage] Vitrage Mascot Selection

Hi, According to the poll we had, Vitrage mascot will be a Giraffe - it's skin looks like a vitrage, and it sees everything from above. Now we should think of how we would like to illustrate it. Should we color the entire Giraffe like a Vitrage? Maybe just part of it? other ideas? (an

Re: [openstack-dev] [vitrage] spec for datasource

From: Yujun Zhang Date: Tuesday, 9 August 2016 at 14:48 1. How do I register a new datasource in an existing system? [yujunz] It seems to be in https://github.com/openstack/vitrage/blob/master/vitrage/datasources/__init__.py Not exactly. This file defines the default datasources to be used. You

Re: [openstack-dev] [vitrage] aodh datasource properties

Hi Yujun, There are few ways to create Aodh alarms. You are referring to event-alarms, and I believe you are right about the bug. Note, however, that for threshold-alarm, the resource_id appears without the “traits” prefix, so Vitrage Aodh datasource should be able to handle both cases. An

[openstack-dev] [nova][vitrage] host evacuate

Hi, In Vitrage project[1], I would like to add an option to call nova host-evacuate for a failed host. I noticed that there is an api for ‘nova evacuate’, and a cli (but no api) for ‘nova host-evacuate’. Is there a way that I can call 'nova host-evacuate’ from Vitrage code? Did you consider

[openstack-dev] [vitrage] Vitrage Mascot Selection

Hi, As we discussed in the IRC meeting today, we should select a Mascot for Vitrage project. Please add your suggestions in the etherpad below: https://etherpad.openstack.org/p/vitrage-mascot We need to select 3-5 leading suggestions, send them to OpenStack representative for evaluation, and

Re: [openstack-dev] [vitrage] Vitrage Mascot Selection

> -Original Message- > From: Afek, Ifat (Nokia - IL) [mailto:ifat.a...@nokia.com] > Sent: Wednesday, July 13, 2016 11:53 AM > > Hi, > > As we discussed in the IRC meeting today, we should select a Mascot for > Vitrage project. > > Please add your sug

Re: [openstack-dev] [vitrage] entity graph layout

Hi, It is possible to adjust the layout of the graph. You can double-click on a vertex and it will remain pinned to its place. You can then move the pinned vertices around to adjust the graph layout. Hope it helped, and let us know if you need additional help with your demo. Best Regards,

Re: [openstack-dev] [vitrage] spec for datasource

Hi Yujun, Please see my answers below. Best Regards, Ifat. From: Yujun Zhang Date: Tuesday, 9 August 2016 at 12:06 For proprietary datasource, I'm considering to adapt the api to common protocol/interface, e.g. RESTful, SNMP and etc and I wish to know how to add support for these interface.

Re: [openstack-dev] [vitrage] entity graph layout

in progress? -- Yujun On Sun, Aug 7, 2016 at 1:09 PM Afek, Ifat (Nokia - IL) <ifat.a...@nokia.com<mailto:ifat.a...@nokia.com>> wrote: Hi, It is possible to adjust the layout of the graph. You can double-click on a vertex and it will remain pinned to its place. You can then mov

Re: [openstack-dev] [nova][vitrage] host evacuate

On 15/08/2016, 19:29, "Matt Riedemann" <mrie...@linux.vnet.ibm.com> wrote: >On 8/15/2016 4:24 AM, Afek, Ifat (Nokia - IL) wrote: >> Hi, >> >> In Vitrage project[1], I would like to add an option to call nova >> host-evacuate for a failed hos

[openstack-dev] [vitrage] Vitrage Ocata release candidate

Hi, Thursday, February 2nd is the deadline for tagging Vitrage release candidates and creating stable/ocata branches. Please make sure all your important changes are pushed before this date. Starting from next week, only bug fixes can be pushed to stable/ocata. The master branch will be used

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

On 30/01/2017, 19:11, "gordon chung" <g...@live.ca> 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? > > A

[openstack-dev] [vitrage] Added Vitrage release notes

Hi, I added release notes for the Vitrage projects. Please go over them, and let me know if I missed an important feature: https://review.openstack.org/#/c/427311/ https://review.openstack.org/#/c/427130/ https://review.openstack.org/#/c/427121/ Note that these changes must be merged before

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

On 02/02/2017, 15:43, "gordon chung" <g...@live.ca> 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

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

On 31/01/2017, 18:43, "gordon chung" <g...@live.ca> 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. Bu

[openstack-dev] [vitrage] Vitrage Hands-On Webinar

Hi, Nokia is hosting a Webinar about Vitrage, tomorrow January 24th at 10:00 a.m. EDT/ 5:00 pm, Northern Europe Time. This will be a hands-on lab, where Dan Offek (a Vitrage core developer) will present an overview of what Vitrage is all about, and guide you through the process of installing,

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

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

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

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" <jul...@danjou.info> wrote: On Tue, Jan 24 2017, Afek, Ifat (Nokia - IL) wrote: > We understood that Aodh a

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

On 25/01/2017, 17:12, "Julien Danjou" <jul...@danjou.info> 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 alarm

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

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

[openstack-dev] [vitrage][ptl] PTL candidacy for Pike

Hi All, I am announcing my candidacy for PTL of the OpenStack Vitrage project for the Pike cycle. I have been the Vitrage PTL from its first day. I was involved in the first stages of the design and implementation (in Mitaka), was thrilled when it became an official OpenStack project only seven

[openstack-dev] [vitrage] New Vitrage project mascot

Hi, This is the new draft of our Giraffe mascot. The illustrators tried to make its skin look more like stained glass. What do you think? Ifat. [cid:image001.png@01D27A3A.128CB9B0] __ OpenStack Development Mailing List

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

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

[openstack-dev] [vitrage] Vitrage logo files

Hi, We received our final logo files. Enjoy ☺ Ifat. From: Heidi Joy Tretheway <heidi...@openstack.org> Date: Tuesday, 14 February 2017 at 01:23 To: "Afek, Ifat (Nokia - IL)" <ifat.a...@nokia.com> Subject: Vitrage logo files Hi Ifat, I’m excited to finally be able to sh

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

From: Yujun Zhang Date: Tuesday, 17 January 2017 at 02:41 Sounds good. Have you created an etherpad page for collecting topics, Ifat? Here: https://etherpad.openstack.org/p/vitrage-pike-design-sessions

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

From: Yujun Zhang <zhangyujun+...@gmail.com> Date: Thursday, 12 January 2017 at 17:37 On Thu, Jan 12, 2017 at 5:12 PM Afek, Ifat (Nokia - IL) <ifat.a...@nokia.com<mailto:ifat.a...@nokia.com>> wrote: 'deduced' vs 'monitored' would be good enough for most cases. Unless we have

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

From: Yujun Zhang Date: Sunday, 15 January 2017 at 17:53 About fault and alarm, what I was thinking about the causal/deducing chain in root cause analysis. Fault state means the resource is not fully functional and it is evaluated by related indicators. There are

[openstack-dev] [vitrage] Vitrage weekly IRC meeting is SKIPPED

Hi, Vitrage IRC meeting tomorrow (Aug 17) will be SKIPPED, as many Vitrage contributors are away. Thanks, Ifat. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [vitrage] entity graph layout

On Mon, Aug 8, 2016 at 2:34 PM Afek, Ifat (Nokia - IL) <ifat.a...@nokia.com<mailto:ifat.a...@nokia.com>> wrote: There is no such blueprint at the moment. You are more than welcome to add one, in case you have some ideas for improvements. Ifat. From: Yujun Zhang Date: Mond

Re: [openstack-dev] [vitrage] relationship_type in static_datasources

From: Yujun Zhang Date: Monday, 5 September 2016 at 13:14 On Mon, Sep 5, 2016 at 5:49 PM Afek, Ifat (Nokia - IL) <ifat.a...@nokia.com<mailto:ifat.a...@nokia.com>> wrote: From: Yujun Zhang Date: Friday, 2 September 2016 at 08:47 ... Cool. Just please note that you can’t push

Re: [openstack-dev] [vitrage] relationship_type in static_datasources

From: Yujun Zhang Date: Friday, 2 September 2016 at 08:47 On Fri, Sep 2, 2016 at 2:44 AM Afek, Ifat (Nokia - IL) <ifat.a...@nokia.com<mailto:ifat.a...@nokia.com>> wrote: I think you have a point. We can indeed use the templates definitions for the static datasources as well

Re: [openstack-dev] [vitrage] relationship_type in static_datasources

ntity discovery from the same file. By reusing the template parsing engine and workflow, we may reduce the work in maintenance and bring in new features more easily. We may discuss it further if anything unclear. On Tue, Aug 30, 2016 at 11:07 PM Afek, Ifat (Nokia - IL) <ifat.a...@

Re: [openstack-dev] [vitrage] relationship_type in static_datasources

Hi Yujun, From: Yujun Zhang Date: Monday, 29 August 2016 at 11:59 entities: - type: switch name: switch-1 id: switch-1 # should be same as name state: available relationships: - type: nova.host name: host-1 id: host-1 # should be same as name is_source:

Re: [openstack-dev] [vitrage] inspecting external openstack environment

Hi Yujun, Using Vitrage for an external openstack environment should be possible, but it has never been tested. There are some issues to consider: * You should set the ip of the keystone in vitrage.conf, and make sure you can access it * You will need to install, together with

[openstack-dev] [vitrage] Vitrage IRC meeting - SKIPPED this week

Hi, Vitrage meeting today will be SKIPPED. We will meet again next week, on September 20. Thanks, Ifat. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [vitrage] PTL candidacy

Hi All, I would like to announce my candidacy to continue as Vitrage PTL for the Ocata release. I've been leading the Vitrage project development from the day it started, in Mitaka. During this time our team has made tremendous progress, and now we have a fully-functional RCA service. The

Re: [openstack-dev] [Vitrage] Installation

Hi Paul, Please find the installation and configuration instructions here: https://github.com/openstack/vitrage/blob/master/doc/source/installation-and-configuration.rst Let us know if you have any other questions, we’ll be happy to help. Best regards, Ifat. From: Paul Vaduva Reply-To:

[openstack-dev] [vitrage] Barcelona design sessions

Hi, As discussed in our IRC meeting today, you are welcome to suggest topics for vitrage design sessions in Barcelona: https://etherpad.openstack.org/p/vitrage-barcelona-design-sessions Thanks, Ifat. __ OpenStack

Re: [openstack-dev] [vitrage] reference a type of alarm in template

Hi Yujun, You understood correctly. ‘name’ is checked if it exists, and is ignored otherwise. Best Regards, Ifat. From: Yujun Zhang Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Wednesday, 17 August 2016 at 18:01 To: "OpenStack Development Mailing List (not for

Re: [openstack-dev] [vitrage][vitrage-dashboard] cropped entity information

Hi Yujun, This is something that we need to handle. You can open a bug about it. Best Regards, Ifat. From: Yujun Zhang Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Wednesday, 17 August 2016 at 07:08 To: "OpenStack Development Mailing List (not for usage

Re: [openstack-dev] Suspected SPAM - Re: [vitrage] relationship_type in static_datasources

`vitrage/evaluator/template_validation/template_syntax_validator.py`. Where is such restriction applied in static_datasources? -- Yujun On Wed, Aug 24, 2016 at 3:19 PM Afek, Ifat (Nokia - IL) <ifat.a...@nokia.com<mailto:ifat.a...@nokia.com>> wrote: Hi Yujun, Indeed, we have some restr

Re: [openstack-dev] [vitrage] relationship_type in static_datasources

Hi Yujun, Indeed, we have some restrictions on the relationship types that can be used in the static datasources. I think we should remove these restrictions, and allow any kind of relationship type. Best regards, Ifat. From: Yujun Zhang Date: Monday, 22 August 2016 at 08:37 I'm following

[openstack-dev] [vitrage] Barcelona design sessions

Hi, There will be three Vitrage design sessions in Barcelona: Wednesday 15:05-15:45: workroom Wednesday 15:55-16:35: fishbowl Wednesday 17:55-18:35: workroom I gathered the ideas that were raised in the etherpad below, and created a draft for the design session discussions. I’ll be happy to

Re: [openstack-dev] [vitrage][aodh] about aodh notifier to create a event alarm

From: "dong.wenj...@zte.com.cn" Date: Wednesday, 19 October 2016 at 09:21 The BP of aodh-message-bus-notifications[1] was blocked as Aodh message bus notification. As the discuession of Vitrage and Aodh in etherpad[2], only the Aodh alarm_deletion notification is

Re: [openstack-dev] [vitrage][aodh] about aodh notifier to create a event alarm

From: "dong.wenj...@zte.com.cn" Date: Wednesday, 19 October 2016 at 11:01 The BP of aodh-message-bus-notifications[1] was blocked as Aodh message bus notification. As the discuession of Vitrage and Aodh in etherpad[2], only the Aodh alarm_deletion notification

[openstack-dev] [vitrage] weekly IRC meetings

Hi all, We will have Vitrage IRC meeting today on the usual time, 08:00 UTC. The meeting next week will be canceled, as most of us will be in Barcelona Summit. Thanks, Ifat. __ OpenStack Development Mailing List (not for

Re: [openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm

Well… long time ago I asked to add another notification topic to Aodh, and you said that you blocked it. If that’s not the case, everything is fine :-) Like I said before, we planned on implementing it in Newton, but unfortunately it didn’t happen. I really hope to improve the Vitrage-Aodh

Re: [openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm

On 20/10/2016, 20:14, "gordon chung" <g...@live.ca> wrote: > >On 20/10/16 01:01 PM, Afek, Ifat (Nokia - IL) wrote: >> Well… long time ago I asked to add another notification topic to Aodh, and >> you said that you blocked it. If that’s not the case, eve

Re: [openstack-dev] [vitrage][aodh] about aodh notifier to create a event alarm

dwj, This would be great! Thanks for your help. Ifat. From: "dong.wenj...@zte.com.cn<mailto:dong.wenj...@zte.com.cn>" Date: Friday, 21 October 2016 at 04:14 To: "Afek, Ifat (Nokia - IL)", gordon chung Cc: "OpenStack Development Mailing List (not for usage ques

[openstack-dev] [vitrage] datasources terminology

Hi, I think we have a confusing terminology in Vitrage datasources. The following parameters are used in the drivers and transformers: * event_type: the type of event/notification that comes from the datasource. For example: ‘compute.instance.delete.end’, ‘volume.detach.start’ *

[openstack-dev] [vitrage] Barcelona Summit recap

Hi, Barcelona summit was very successful and productive for the Vitrage team. Below is a summary of our main activities during the summit. Sessions 1. Keynotes demo - OpenStack and OPNFV - Keeping Your Mobile Phone Calls Connected Ifat Afek, Ryota Mibu and Ildiko Vancsa presented

Re: [openstack-dev] [vitrage]bp:static-datasource-config-formatworking items

From: Yujun Zhang Date: Tuesday, 15 November 2016 at 16:03 On Tue, Nov 15, 2016 at 8:44 PM Weyl, Alexey (Nokia - IL) > wrote: Ok, sounds good. We need to understand what is the common way in openstack to work with deprecated code. Maybe it

[openstack-dev] [vitrage] FW: Your draft logo & sneak peek

Hi, Please find below the draft for the Vitrage Giraffe. If you would like to provide feedback on the design, you can use: http://tinyurl.com/OSmascot Note that the original idea was to have a colourful Giraffe, with a skin that looks like a Vitrage. Here's a 50-second "sneak peek" at how they

Re: [openstack-dev] [vitrage][aodh] about aodh notifier to create a event alarm

Hi dwj, Thanks for bringing this up. Aodh notifier plugin inside Vitrage is defined as a POC, and is disabled by default. We are aware that this integration is not working well, and its purpose was to demonstrate how it could work and start a discussion about other possible implementations. I

Re: [openstack-dev] Suspected SPAM - [vitrage] datasources terminology

it. * datasource_action: the type of action that was performed by the driver: init_snapshot, snapshot or update. What do you think? Ifat. From: "Afek, Ifat (Nokia - IL)" Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Tuesday, 29 November 2016 at 09:26 To: &q

[openstack-dev] [vitrage] Vitrage road map

Hi, I created a new wiki page for Vitrage road map[1] . I listed there the current tasks we are working on for Ocata, and some high priority tasks that we might not have time to complete in this (short) version. Feel free to suggest new tasks, either in this page or as a blueprint. And of

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

Hi Yujun, See my comments inline. Ifat. From: Yujun Zhang Date: Wednesday, 11 January 2017 at 12:12 I have just realized abstract alarm is not a good term. What I was talking about is fault and alarm. Fault is what actually happens, and alarm is how it is detected

Re: [openstack-dev] 答复: Re: [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

Hi Yinliyin, There are two use cases: One is yours, where you have a single monitor that generates “real” alarms, and Vitrage that generates deduced alarms. Another is where someone has a few monitors, and there might be a collision/equivalence between their alarms. The solution that you

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

om.cn" <gong.yah...@zte.com.cn> Subject: Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator Hi, Ifat If I understand it correctly, your concerns are mainly on same alarm from different monitor, but not "suspect" s

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

Hi YinLiYin, This is an interesting question. Let me divide my answer to two parts. First, the case that you described with Nagios and Vitrage. This problem depends on the specific Nagios tests that you configure in your system, as well as on the Vitrage templates that you use. For example,

Re: [openstack-dev] [Vitrage] About introduce suspect state of a alarm

Hi YinLiYin, I’m not sure I understood the use case. Are you using a monitor that raises alarms A, B, C, D, and E? or does the monitor raise only alarms A and C, and the other alarms are deduced alarms created by Vitrage? In Vitrage templates you can determine causal relationship between

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

tp://docs.openstack.org/developer/vitrage/scenario-evaluator.html#concepts-and-guidelines On Sat, Jan 7, 2017 at 2:23 AM Afek, Ifat (Nokia - IL) <ifat.a...@nokia.com<mailto:ifat.a...@nokia.com>> wrote: Hi YinLiYin, This is an interesting question. Let me divide my answer to two parts.

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

.yuj...@zte.com.cn" <zhang.yuj...@zte.com.cn> Subject: Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator Maybe I have missed something in the scenario template, but it seems you have understood my idea quite correctly :-) See

Re: [openstack-dev] [Vitrage] About alarms reported by datasource and the alarms generated by vitrage evaluator

?) So I don’t think that making this change is beneficial. What do you think? Best Regards, Ifat. From: "yinli...@zte.com.cn" <yinli...@zte.com.cn> Date: Monday, 9 January 2017 at 05:29 To: "Afek, Ifat (Nokia - IL)" <ifat.a...@nokia.com> Cc: "openstack-de

[openstack-dev] [vitrage] no IRC meeting next week

Hi, The next IRC meeting on December 28 will be canceled due to the holidays. We will meet again on Wednesday, January 4th. Best Regards, Ifat. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

  1   2   3   >