Re: [openstack-dev] [vitrage] update_timestamp precision

Hi Eric, Apparently we have inconsistent behavior between the different datasources. The format of the timestamp should be '%Y-%m-%dT%H:%M:%SZ' as defined in [1]. We need to go over the code and make sure all datasources are aligned. I created a bug for it [2]. [1] https://github.com/openstac

Re: [openstack-dev] [vitrage] matching webhook vs alarm list

Hi Eric, The format of the vitrage_id was changed to UUID in Pike release. It appears that the API documentation [1] is outdated. I’ll fix it. The vitrage_id that you get in the webhook notification should match the one coming from ‘vitrage alarm list’. The ‘id’ field is determined by the extern

[openstack-dev] [vitrage] No IRC meeting this week

Hi, The IRC meeting this week is canceled, since many Vitrage developers are on vacation. We will meet next Wednesday, June 6th, at 8:00 UTC. See you next week, Ifat __ OpenStack Development Mailing List (not for usage que

[openstack-dev] [vitrage] etherpads for Vitrage forum sessions

Hi, I created etherpads for Vitrage forum sessions: - Advanced RCA use cases - taking Vitrage to the next level: https://etherpad.openstack.org/p/YVR-vitrage-advanced-use-cases - Vitrage RCA over K8s. Pets and Cattle - Monitor each cow? : https://etherpad.openstack.org/p/YVR-vitrage-rca-over-

Re: [openstack-dev] [Vitrage] Vitrage graph error

the CLI does not seem to work either. I'll check it out with you. : ) Thank you. Best Regards, Minwook. From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com] Sent: Tuesday, April 24, 2018 4:15 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re

Re: [openstack-dev] [Vitrage] Vitrage graph error

Hi Minwook, Is the problem only in the Entity Graph? Do the Alarms view and the Topology view work? And what about the CLI? I’ll check it and get back to you. Thanks, Ifat From: MinWookKim Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Monday, 23 April 2018

Re: [openstack-dev] [mistral] [vitrage] Propose adding Vitrage's actions to Mistral Actions

From: Renat Akhmerov Date: Monday, 23 April 2018 at 9:45 On 23 Apr 2018, 13:38 +0700, Jaewook Oh , wrote: Hello Mistral and Vitrage team, I've been testing vitrage with mistral workflow, but it seems that there are no Vitrage actions in Mistral yet. I think Vitrage actions should be added t

[openstack-dev] [vitrage] No IRC meeting this week

Hi, The IRC meeting tomorrow (April 18th) is canceled, as many Vitrage developers will be on vacation. See you next week, Ifat __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ.

Re: [openstack-dev] [Vitrage] New proposal for analysis.

an cause constant overhead. And Zabbix history can be another task for Vitrage. If we configure the agents themselves and exclude the VM's internal checks, we can provide functionality with simple code. how is it? Thank you. Best regards, Minwook. From: Afek, Ifat (Nokia - IL/Kfar Sava) [ma

Re: [openstack-dev] [Vitrage] New proposal for analysis.

function. If I think wrong, please tell me anytime. :) Thank you. Best regards, Minwook. From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com] Sent: Sunday, April 1, 2018 3:40 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Vitrage

Re: [openstack-dev] [Vitrage] New proposal for analysis.

ult. I think that part will be able to talk in detail later. My answer is my opinions and assumptions. If you think my implementation is wrong, or an inefficient implementation, please do not hesitate to tell me. Thanks. Best Regards, Minwook. From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.

Re: [openstack-dev] [Vitrage] New proposal for analysis.

etail later. My answer is my opinions and assumptions. If you think my implementation is wrong, or an inefficient implementation, please do not hesitate to tell me. Thanks. Best Regards, Minwook. From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com] Sent: Wednesday, March 28, 2018

[openstack-dev] [vitrage] Next two IRC meetings are canceled

Hi, Most of Vitrage developers will not be available today and next Wednesday, so we’ll skip the next two IRC meetings. We will meet again on Wednesday, April 11. Thanks, Ifat __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [Vitrage] New proposal for analysis.

Hi Minwook, I think that from a user’s perspective, these are very good ideas. I have some questions regarding the UX and the implementation, since I’m trying to think what could be the best way to execute such actions from Vitrage. · I assume that these checks will not be implemented

Re: [openstack-dev] [vitrage] Nominating Dong Wenjuan for Vitrage core

: Re: [openstack-dev] [vitrage] Nominating Dong Wenjuan for Vitrage core +2 On 21 March 2018 at 16:37, Afek, Ifat (Nokia - IL/Kfar Sava) mailto:ifat.a...@nokia.com>> wrote: Hi, I would like to nominate Dong Wenjuan for Vitrage core. Wenjuan has been contributing to Vitrage for a long time,

[openstack-dev] [vitrage] Nominating Dong Wenjuan for Vitrage core

Hi, I would like to nominate Dong Wenjuan for Vitrage core. Wenjuan has been contributing to Vitrage for a long time, since Newton version. She implemented several important features and has a deep knowledge of Vitrage architecture. I’m sure she can be a great addition to our team. Thanks, Ifat

[openstack-dev] [vitrage] alarm and resource equivalence

Hi, Since we need to design these days both alarm equivalence/merge [1] and resource equivalence/merge features, I thought it might be a good idea to start with a use cases document. Let’s agree on the requirements, and then see if we can come up with a design that matches both cases. I pushed

[openstack-dev] [vitrage] No IRC meeting today

Hi, We will not hold the weekly IRC meeting today due to the PTG discussions. We will meet again next week, March 6th. BR, Ifat __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ.

[openstack-dev] [vitrage][ptg] Vitrage PTG agenda

Hi, Vitrage PTG discussions will start today at 9:00 Dublin time. You are all welcome to join. We will hold the discussions on webex, so you can join remotely as well. PTG etherpad: https://etherpad.openstack.org/p/vitrage-ptg-rocky See you soon, Ifat __

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

, 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

ogically posible to create The scenario we need, Scenario I. Best Regards Paul 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) mailto:openstack-dev@lists.openstack.org>&

[openstack-dev] [vitrage] Tagged Vitrage release candidates and created stable/queens branches

Hi, I tagged the following release candidates for Vitrage: vitrage 2.1.0 vitrage-dashboard 1.4.1 python-vitrageclient 2.0.0 (already tagged) All these repositories now have stable/queens branches, so the master can be used for Rocky development. Thanks, Ifat.

Re: [openstack-dev] [heat][horizon][ironic][neutron][swift][tricircle][vitrage][watcher] Help needed for your release

Hi, I will request to a create stable/queens branch for Vitrage later today. Thanks, Ifat. On 07/02/2018, 18:49, "Matthew Thode" wrote: On 18-02-07 16:33:52, Luke Hinds wrote: > On Wed, Feb 7, 2018 at 4:23 PM, Matthew Thode > wrote: > > > Hi all, > > > > it looks

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

ve events for raising the alarm and also for clearing it is that correct? Best Regards, Paul From: 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) Subject: Re: [openstack-dev

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 find a vitrage version 1.3.1. Could it be that you are referring to a ver

Re: [openstack-dev] [vitrage][ptl] PTL candidacy for Rocky

Sorry for the copy&paste problem in the previous email… Ifat On 01/02/2018, 15:24, "Afek, Ifat (Nokia - IL/Kfar Sava)" wrote: Hi all, I would like to announce my candidacy to continue as Vitrage PTL for the Rocky release. I’ve been the PTL of Vitrage

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

Hi all, I would like to announce my candidacy to continue as Vitrage PTL for the Rocky release. I’ve been the PTL of Vitrage since the day it started, in the Mitaka release. I think we have made an amazing journey, and we now have a mature, stable and well known project. During the Queens cycle o

[openstack-dev] [vitrage] Vitrage templates are now loaded using a new API

Hi, A new API for Vitrage template add and template delete was added this week. As part of this change, Vitrage templates are now stored in a database and are no longer read from the file system. In case you are using templates, make sure to call the new API and add them to Vitrage once you get

Re: [openstack-dev] [requirements] [vitrage][glance] global requirements update for python-vitrageclient

Adding Glance team. Any idea what could be wrong? Thanks, Ifat. On 25/01/2018, 9:09, "Afek, Ifat (Nokia - IL/Kfar Sava)" wrote: Hi, I tried to update the version of python-vitrageclient [1], but the legacy-requirements-integration-dsvm test failed with an error tha

[openstack-dev] [requirements] [vitrage] global requirements update for python-vitrageclient

Hi, I tried to update the version of python-vitrageclient [1], but the legacy-requirements-integration-dsvm test failed with an error that does not seem related to my changes: error: can't copy 'etc/glance-image-import.conf': doesn't exist or not a regular file I noticed that two other change

Re: [openstack-dev] [vitrage] rules in vitrage_aggregated_state()

rent developers may already get used to it, but it gives new contributors too many surprises. What do you think? Shall we amend them? On Tue, Jan 9, 2018 at 11:29 PM Afek, Ifat (Nokia - IL/Kfar Sava) mailto:ifat.a...@nokia.com>> wrote: Hi, I agree that the code is confusing… This is part

Re: [openstack-dev] [congress] generic push driver

From: Eric K Date: Tuesday, 9 January 2018 at 0:43 Hi Ifat, From: "Afek, Ifat (Nokia - IL/Kfar Sava)" mailto:ifat.a...@nokia.com>> Date: Sunday, January 7, 2018 at 4:00 AM Hi Eric, I have two questions: 1. An alarm is usually raised on a resource, and in Vitrage

Re: [openstack-dev] [vitrage] rules in vitrage_aggregated_state()

Hi, I agree that the code is confusing… This is part of a change that was made in order to support default states for static entities. For example, in the static configuration yaml file you can add entities of types ‘switch’ and ‘br-ex’. In the past, in order to support states for these new ty

Re: [openstack-dev] [congress] generic push driver

Hi Eric, I have two questions: 1. An alarm is usually raised on a resource, and in Vitrage we can send you the details of that resource. Is there a way in Congress for the alarm to reference a resource that exists in another table? And what if the resource does not exist in Congress? 2

[openstack-dev] [vitrage] No IRC meeting this week

Hi, The IRC meeting on the coming Wednesday, Dec 27th, is canceled. Thanks, Ifat __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http

[openstack-dev] [requirements][vitrage] Networkx version 2.0

Hi, There is an open bug in launchpad about the new release of Networkx 2.0, that is backward incompatible with versions 1.x [1]. Is there a plan to change the Networkx version in the global requirements in Queens? We need to make some code refactoring in Vitrage, and I’m trying to understand h

Re: [openstack-dev] [OpenStack][Vitrage] Vitrage Entity Graph supports various actions according to mouse events for entities.

n enter the required parameters for this. ) As such, we can discuss the list to be included in the right mouse button action. what do you think? Best Regards, Minwook. From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com] Sent: Thursday, December 14, 2017 11:18 PM To: OpenStack

[openstack-dev] [oslo][requirements][vitrage] oslo.service 1.28.1 breaks Vitrage gate

Hi, The latest release of oslo.service 1.28.1 breaks the Vitrage gate. We are creating several threads and timers [1], but only the first thread is executed. We noticed that Trove project already reported this problem [2]. Please help us fix it. Thanks, Ifat. [1] https://github.com/

Re: [openstack-dev] [OpenStack][Vitrage] Vitrage Entity Graph supports various actions according to mouse events for entities.

Hi MinWookKim, I think that the right click is a good idea. Some questions: · Just to make sure I understood correctly – after the “performance and load test”, do you expect to see the result on the selected resource, or somewhere else? · What do you mean by “set monitoring c

Re: [openstack-dev] [vitrage] Feedback on ability to 'suppress' alarms by type and/or resource in Vitrage

etimes verbose ‘name’ (description) field of the alarm. But i realize it would be difficult to enforce / manage the usage of this field. This is a lower priority item for me. Greg. From: "Afek, Ifat (Nokia - IL/Kfar Sava)" Reply-To: "openstack-dev@lists.openstack.org"

Re: [openstack-dev] [vitrage] Feedback on ability to 'suppress' alarms by type and/or resource in Vitrage

Hi Greg, First, I think that supporting alarm suppression in Vitrage is a very good idea. One question that I have is: I understand that you plan to support it both in the UI and in the CLI. Do you want to the suppression to be per-user? per-tenant? global? Regarding adding vitrage_alarm_type,

[openstack-dev] [vitrage] required changes on existing devstacks

Hi, Due to the latest changes of the event persistor service in Vitrage[1], there is a need to run vitrage-dbsync on any existing devstack: · Pull the latest changes of vitrage (if you pulled yesterday you should pull again) · Run: vitrage-dbsync [1] https://review.openstack.

[openstack-dev] [vitrage] Reminder: Vitrage virtual PTG this week

Hi, We will hold the Vitrage Queens virtual PTG this week, on October 17-19. You are welcome to join! More details can be found in the etherpad[1]. The regular weekly IRC meeting will be canceled. [1] https://etherpad.openstack.org/p/vitrage-ptg-queens Thanks, Ifat. ___

Re: [openstack-dev] [vitrage] Question about vitrage workings.

Hi Paul, Vitrage is supposed to be automatically updated when a VM is deleted from Nova. There are a few issues I would check in your case. 1. You said that you were using vitrage 1.3.1. The Newton version of vitrage is 1.3.0, there is no 1.3.1 version. Maybe you meant vitrage-dashboard

[openstack-dev] FW: [vitrage]Vitrage Devstack on master

From: "Hefetz, Idan (Nokia - IL/Kfar Sava)" Hi, To use Vitrage Devstack on master, please notice that after this commit, a few steps are required: 1. Add the following to /etc/vitrage/vitrage.conf [database] connection = mysql+pymysql://root:pas

[openstack-dev] [vitrage] No IRC meeting this week

Hi, The IRC meeting this week is canceled, as many Vitrage contributors will be on vacation. Next week we will hold the Vitrage virtual PTG on Tue-Thu, October 17-19. More details can be found in the etherpad: https://etherpad.openstack.org/p/vitrage-ptg-queens Best Regards, Ifat.

[openstack-dev] [vitrage] Vitrage virtual PTG

Hi, We will hold the Vitrage virtual PTG on October 17-19. I have created an initial schedule draft, you are more than welcome to comment or suggest new topics for discussion: https://etherpad.openstack.org/p/vitrage-ptg-queens Best Regards, Ifat. __

Re: [openstack-dev] [vitrage] Extending Topology

Hi Usman, Great to hear back from you ☺ You are more than welcome to join our efforts. You can look at the list of blueprints[1], suggest new ones, implement existing, or solve bugs[2]. Whatever you chose, we will be happy to assist. The ways to contact Vitrage developers are here in the maili

[openstack-dev] [vitrage] No IRC meeting this week

Hi, The IRC meeting on the coming Wednesday (September 20th) is canceled, as many Vitrage contributors will be on vacation. We will meet again next week, on September 27th. Best Regards, Ifat. __ OpenStack Development Mail

[openstack-dev] [vitrage] Vitrage Queens virtual PTG

Hi All, As agreed in Doodle[1] and in today’s IRC meeting[2], We will hold the Vitrage Virtual PTG on the following dates (all times are UTC): Tue, October 17: 6:30-9:30, 10:30-12:00 Wed, October 18: 6:30-9:30 Thu, October 19 (Optional): 6:30-9:30, 10:30-12:00 Feel free to add your name and

Re: [openstack-dev] [vitrage] Collectd - to - Vitrage setup issues

Hi Greg, Can you please send me the vitrage-graph.log? Thanks, Ifat. From: "Waines, Greg" Date: Wednesday, 6 September 2017 at 3:07 To: "Afek, Ifat (Nokia - IL/Kfar Sava)" , "OpenStack Development Mailing List (not for usage questions)" Cc: "TAHHAN, M

Re: [openstack-dev] [vitrage] Collectd - to - Vitrage setup issues

send me the file and I’ll have a look. Best Regards, Ifat. From: "Waines, Greg" Date: Tuesday, 5 September 2017 at 15:38 To: "Afek, Ifat (Nokia - IL/Kfar Sava)" , "OpenStack Development Mailing List (not for usage questions)" Cc: "TAHHAN, MARYAM"

Re: [openstack-dev] [all] connecting nova notification users and developers

Hi, Vitrage holds a topology graph with all resources in the system and the relationships between them, for fault correlation purposes[1]. It uses notifications from Nova (as well as from other components) to update its internal state[2]. It is important for us to get immediate notifications

Re: [openstack-dev] [vitrage] Collectd - to - Vitrage setup issues

Hi Greg, You should access the vitrage-graph.log using journalctl: sudo journalctl --no-pager --unit devstack@vitrage-graph.service<mailto:devstack@vitrage-graph.service> Best Regards, Ifat. From: "Waines, Greg" Date: Thursday, 31 August 2017 at 20:10 To: "Afek, Ifat

Re: [openstack-dev] [vitrage] Collectd - to - Vitrage setup issues

"OpenStack Development Mailing List (not for usage questions)" Cc: "Afek, Ifat (Nokia - IL/Kfar Sava)" , "TAHHAN, MARYAM" Subject: Re: [openstack-dev] [vitrage] Collectd - to - Vitrage setup issues Hi Ifat, thanks for the reply ... just got around to trying your suggestions

[openstack-dev] [vitrage] Vitrage Queens virtual PTG

Hi all, As Vitrage will not participate in the Denver PTG, we decided to hold a virtual PTG instead. I created an etherpad[1] with a list of topics to discuss, and a Doodle poll[2] for selecting the date. I believe that two days will be enough. If you would like to participate, please add your

Re: [openstack-dev] [vitrage] Collectd - to - Vitrage setup issues

Hi Greg, I’m less familiar with the collectd configuration and the events that it sends. Regarding the collectd_conf.yaml, it is definitely missing. You should add a /etc/vitrage/collectd_conf.yaml file that looks like that: collectd: - collectd_host: type: name: - collectd_host: … T

[openstack-dev] [vitrage][mistral] Announcing Vitrage integration with Mistral

Hi all, I’d like to announce the Vitrage integration with Mistral that was developed in Pike cycle. As part of this integration, the Vitrage user can specify in a Vitrage template that in case a certain condition is met a Mistral workflow should be executed. The condition can include a combin

[openstack-dev] [vitrage][ptl] PTL on vacation

Hi, I’m going to be on vacation between August 17th and 26th. Idan Hefetz (idan_hefetz on IRC) will replace me while I’m away and will manage the Vitrage release. Thanks, Ifat. __ OpenStack Development Mailing List (not fo

Re: [openstack-dev] [vitrage] stable/pike branch for vitrage

On 09/08/2017, 3:41, "Tony Breeds" wrote: On Tue, Aug 08, 2017 at 08:17:48AM +0000, Afek, Ifat (Nokia - IL/Kfar Sava) wrote: > Hi, > > I’m going to create stable/pike branches for vitrage and vitrage-dashboard tomorrow or the day after. > If you ha

[openstack-dev] [vitrage] stable/pike branch for vitrage

Hi, I’m going to create stable/pike branches for vitrage and vitrage-dashboard tomorrow or the day after. If you have changes that should enter Pike, try to push them today. After that, we will be able to fix Pike bugs on top of stable/pike for two more weeks. Please do not merge changes that sh

[openstack-dev] [elections][vitrage] Queens PTL candidacy

Hi All, I would like to announce my candidacy for the Vitrage PTL for the Queens release. I've been leading the Vitrage project development from the day it started, two years ago. During this time we have made a tremendous progress, and now we have a stable, well-known project that is running in

[openstack-dev] [vitrage] New Vitrage releases

Hi, We have new releases for Vitrage: vitrage 1.7.0 python-vitrgeclient 1.3.0 vitrage-dashboard 1.3.0 For python-vitrageclient this is the final Pike release, as today is the final release date for client libraries. A stable/pike branch was created for critical bug fixes. The master branch can

Re: [openstack-dev] [Vitrage] Collectd notification isn't shown on the Vitrage Graph

this patch[1] for your demo. [1] https://review.openstack.org/#/c/484300 Let me know if it helped, Ifat. From: "Afek, Ifat (Nokia - IL/Kfar Sava)" Date: Sunday, 16 July 2017 at 12:28 To: "OpenStack Development Mailing List (not for usage questions)" Cc: "Tah

Re: [openstack-dev] [Vitrage] Collectd notification isn't shown on the Vitrage Graph

Thank you for fixing the issue. The patch works and I’m able to map the alarm to port now. Also, as a workaround, I was able to fix/resolve the issue by creating the static datasource (attached static_port.yaml) and disabling the neutron port datasource in the vitrage.conf. Ano

Re: [openstack-dev] [Vitrage] Vitrage-Mistral integration problem

Hi Volodymyr, The Vitrage-Mistral integration is still WIP, so it is possible that something was broken. I hope to finish the development in a few days, and I will definitely check your patch as part of it. I’ll update you once I’m done. Best Regards and thanks for the patch, Ifat. From: "Myt

Re: [openstack-dev] [Vitrage] Collectd notification isn't shown on the Vitrage Graph

ph. The ovs port name in collectd ovs_events plugin is identified by the ‘plugin_instance’ notification field. Thanks and Regards, Volodymyr From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com] Sent: Tuesday, July 11, 2017 12:00 PM To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [Vitrage] Collectd notification isn't shown on the Vitrage Graph

raph Hi Ifat, I’ve tested the template file modified by you with enabled debug for the Vitrage graph. See all Vitrage logs in the attachments. Thank you! Best Regards, Volodymyr From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com] Sent: Friday, July 7, 2017 12:42 PM To: OpenStack Deve

Re: [openstack-dev] [Vitrage] [aodh] Integration with doctor

Hi dwj, Adding [aodh] for item #2. Please see my answers inline. Best Regards, Ifat. From: "dong.wenj...@zte.com.cn" Date: Friday, 7 July 2017 at 10:53 Hi, For the integration Vitrage with doctor, I have some issues which need to be confirmed~ :) 1. Notification strategies: conserv

Re: [openstack-dev] [Vitrage] Collectd notification isn't shown on the Vitrage Graph

Now with the file attached From: "Afek, Ifat (Nokia - IL/Kfar Sava)" Date: Friday, 7 July 2017 at 12:41 To: "OpenStack Development Mailing List (not for usage questions)" Cc: "Tahhan, Maryam" Subject: Re: [openstack-dev] [Vitrage] Collectd notification isn

Re: [openstack-dev] [Vitrage] Collectd notification isn't shown on the Vitrage Graph

to attach the topology dump. Attaching it now. Also, I’ve checked the topology, and looks like there is no relationship between neutron port and the alarm for some reason. Thanks and Regards, Volodymyr From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com] Sent: Friday, July 7, 20

Re: [openstack-dev] [Vitrage] Collectd notification isn't shown on the Vitrage Graph

state: ERROR Thanks and Regards, Volodymyr From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com] Sent: Thursday, July 6, 2017 10:01 PM To: OpenStack Development Mailing List (not for usage questions) Cc: Tahhan, Maryam Subject: Re: [openstack-dev] [Vitrage] Collectd notif

Re: [openstack-dev] [Vitrage] Collectd notification isn't shown on the Vitrage Graph

Hi Volodymyr, Let me see if I understood the problem correctly. Are my assumptions right? · You see the neutron port in your entity graph, and it is connected to the VM · You see the alarm on the alarms view, and its resources is the neutron port · You see the alarm in

Re: [openstack-dev] [vitrage] status of blueprint crud-templates

Hi Yujun, We have discussed the templates CRUD in the past, but did not do a detailed design - we only implemented the templates validation as a first phase. You are more than welcome to take the blueprint. Some issues we talked about: · The templates should be stored in a database an

Re: [openstack-dev] [vitrage] Nominating Yujun Zhang to Vitrage core

-- > From: Afek, Ifat (Nokia - IL/Kfar Sava) > [mailto:ifat.a...@nokia.com<mailto:ifat.a...@nokia.com>] > Sent: Sunday, June 25, 2017 3:18 PM > To: OpenStack Development Mailing List (not for usage questions) > mailto:openstack-dev@lists.openstack.org>> > > Hi, &

[openstack-dev] [vitrage] Nominating Yujun Zhang to Vitrage core

Hi, I’d like to nominate Yujun Zhang to the Vitrage core team. In the last year Yujun has made a significant contribution in Vitrage[1], both by adding new features and by reviewing other people’s work. He has an extensive knowledge of the Vitrage architecture and code, and I believe he would

Re: [openstack-dev] [vitrage] First Vitrage Pike release by the end of this week

t;yinli...@zte.com.cn" Subject: Re: [openstack-dev] [vitrage] First Vitrage Pike release by the end of this week Is it done yet? How to fetch the released version for downstream developing? On Tue, Jun 6, 2017 at 2:17 PM Afek, Ifat (Nokia - IL/Kfar Sava) mailto:ifat.a...@nokia.com>>

Re: [openstack-dev] [vitrage-dashboard] Alarm Header Blueprint

7 at 14:58 To: "OpenStack Development Mailing List (not for usage questions)" Cc: "Heller, Alon (Nokia - IL/Kfar Sava)" , "Afek, Ifat (Nokia - IL/Kfar Sava)" Subject: [openstack-dev] [vitrage-dashboard] Alarm Header Blueprint I have registered a new blueprint

[openstack-dev] [vitrage] How to add a release notes file to Vitrage

Hi, In order to add a release notes file to Vitrage, please perform the following: $ cd /opt/stack/vitrage $ reno new my_new_feature Created new notes file in releasenotes/notes/my_new_feature-5e88573b6d99abbb.yaml Edit the file, remove everything that you don’t need, and write 3-4 lines of des

[openstack-dev] [vitrage] First Vitrage Pike release by the end of this week

Hi, Pike-2 milestone is at the end of this week, and although we are not working by the milestones model (we are working by a cycle-with-intermediary model) we need to have the first Vitrage Pike release by the end of this week. I would like to release vitrage, python-vitrageclient and vitrage-

Re: [openstack-dev] [vitrage] error handling

From: "Yujun Zhang (ZTE)" Date: Thursday, 1 June 2017 at 18:10 On Thu, Jun 1, 2017 at 10:49 PM Afek, Ifat (Nokia - IL/Kfar Sava) mailto:ifat.a...@nokia.com>> wrote: So for now we agree that we need to add a UI for configuration information and datasources status. Sounds g

[openstack-dev] [vitrage] Gate issues

Hi, Note that we are currently having problems with the Vitrage gate tests, related to python-setuptools. Other projects experience similar problems. We hope to fix it by the beginning of next week. Best Regards, Ifat. __

Re: [openstack-dev] [vitrage] error handling

11:50 To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [vitrage] error handling On Tue, May 30, 2017 at 3:59 PM Afek, Ifat (Nokia - IL/Kfar Sava) mailto:ifat.a...@nokia.com>> wrote: Hi Yujun, You started an interesting discussion. I t

Re: [openstack-dev] [vitrage] error handling

Hi Yujun, You started an interesting discussion. I think that the distinction between an operational error and a programmer error is correct and we should always keep that in mind. I agree that having an overall design for error handling in Vitrage is a good idea; but I disagree that until the

[openstack-dev] [vitrage] No IRC meeting this week

Hi, We will not hold the Vitrage weekly IRC meeting this week, as many Vitrage contributors will be on vacation. We will meet again next week, on June 7th. Thanks, Ifat. __ OpenStack Development Mailing List (not for usage

[openstack-dev] [vitrage] Vitrage attendance in the PTG in September

Hi, The next PTG (Project Team Gathering) will be held in Denver in September. We need to decide whether we would like to reserve a room for Vitrage, where we could hold design sessions for the next release. What do you say? Are you interested in attending the PTG? Thanks, Ifat. _

Re: [openstack-dev] [vitrage] [nova] VM Heartbeat / Healthcheck Monitoring

On 16/05/2017, 4:36, "Sam P" wrote: Hi Greg, In Masakari [0] for VMHA, we have already implemented some what similar function in masakri-monitors. Masakari-monitors runs on nova-compute node, and monitors the host, process or instance failures. Masakari instance

Re: [openstack-dev] [vitrage] [nova] VM Heartbeat / Healthcheck Monitoring

Hi Greg, If I understand correctly, you would like to add a test that checks if for every VM a heartbeat was retrieved in the last x seconds. Right? Vitrage is not designed to perform such tests. Vitrage datasources retrieve topology (either by polling or by notifications) from services like No

Re: [openstack-dev] trouble installing Nagios on devstack on ubuntu 16.04 ...

Hi Greg, Sorry for not responding earlier about your Nagios problem, most of the Vitrage team is busy preparing to Boston. We have already heard about the Ubuntu 16.04 issue but didn’t investigate it yet, so unfortunately I don’t have a solution for you at the moment. If you are only intereste

Re: [openstack-dev] [vitrage] Alarm Banner for Vitrage Dashboard ?

d River attending. thanks for the input, Greg. From: "Afek, Ifat (Nokia - IL/Kfar Sava)" Reply-To: "openstack-dev@lists.openstack.org" Date: Wednesday, May 3, 2017 at 3:02 AM To: "openstack-dev@lists.openstack.org" Subject: Re: [openstack-dev] [vitrage] Alarm Bann

Re: [openstack-dev] [vitrage] Alarm Banner for Vitrage Dashboard ?

Hi Greg, It sounds like a great idea. Do you plan to show this banner in all Horizon menus (your screenshot shows “Compute/Instances”), or just in Vitrage? for the first option I think you would need to write the code in Horizon itself, not in vitrage-dashboard. Let me know if you need any assi

[openstack-dev] [vitrage] The next two IRC meetings are SKIPPED

Hi, Due to the Boston summit and the fact that most of Vitrage contributors are now busy preparing to it, we will skip the IRC meetings this week and next week. We will meet again on Wednesday, May 17 at 8:00 UTC. Thanks, Ifat. __

[openstack-dev] [vitrage] Change in Vitrage ID

Hi, A change that was committed today[0] modifies the Vitrage ID generation method. Instead of computing the vitrage-id based on the resource properties, it is now created as a standard OpenStack UUID. Note that this change might affect your workflow, in case you counted on the previous name ge

Re: [openstack-dev] Boston Forum Schedule

Hi, The scheduled time for the Vitrage forum session is highly inconvenient, as it starts immediately after another Vitrage session. Is it possible to reschedule? Seems like Wednesday 15:30-16:10 is available – can we take it instead? Thanks, Ifat. On 10/04/2017, 12:35, "Tom Fifield" wrote:

[openstack-dev] [vitrage] Next Vitrage IRC meeting will be SKIPPED

Hi, As many Vitrage developers will be on vacation next week, the IRC meeting on April 12 will be SKIPPED. We will meet again on April 19. Thanks, Ifat. __ OpenStack Development Mailing List (not for usage questions) Unsubs

Re: [openstack-dev] Project Navigator Updates - Feedback Request

, 30 March 2017 at 19:23 To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] Project Navigator Updates - Feedback Request Afek, Ifat (Nokia - IL/Kfar Sava)<mailto:ifat.a...@nokia.com> March 30, 2017 at 11:01 AM Under “API Versions” t

Re: [openstack-dev] Project Navigator Updates - Feedback Request

Thanks Lauren, A few issues regarding the Vitrage page: · Vitrage is currently listed under “Management Tools” category. As a Root Cause Analysis service, it doesn’t manage anything, just provides insights to the user (or to other projects). Can you please move it under ‘Data and Anal

Re: [openstack-dev] [vitrage] Extending Topology

es I agree, if you want to keep compute hierarchy separate then addition of networking components is not a good idea. Also, suggestions from other vitrage members are welcomed. > On Thu, Mar 16, 2017 at 6:44 PM, Afek, Ifat (Nokia - IL) < > ifat.a..

Re: [openstack-dev] [vitrage] vitrage Resource API

Hi dwj, The resource API is something that we planned on implementing, but eventually didn’t do that. Best Regards, Ifat. From: "dong.wenj...@zte.com.cn" Date: Tuesday, 21 March 2017 at 02:45 To: "trinath.soman...@nxp.com" Cc: "openstack-dev@lists.openstack.org&qu

Re: [openstack-dev] [vitrage] what is "API to register on Vitrage notificaitons"

Yes, that’s the right blueprint. Best Regards, Ifat. From: "Yujun Zhang (ZTE)" Date: Thursday, 16 March 2017 at 18:14 Hi root causers I want to confirm some detail about one subject in vitrage Pike roadmap · API to register on Vitrage notificaitons Is it linked to blueprint https://

  1   2   3   >