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

Zhang to Vitrage core Hi, I added Yujun Zhang to the vitrage-core team. Yujun, Welcome ☺ Best Regards, Ifat. From: דני אופק <dany.of...@gmail.com<mailto:dany.of...@gmail.com>> Date: Monday, 26 June 2017 at 11:00 +1 On Mon, Jun 26, 2017 at 7:45 AM, Weyl, Alexey (Nokia - IL/Kfa

[openstack-dev] [Vitrage] New service in Vitrage

Hi, We have added a new service to Vitrage, called vitrage-collector. Vitrage-collector is part of our HA (High Availability) solution. At the moment, until we'll finish to write the history, after restarting the vitrage-graph you have to restart the vitrage-collector as well. BR, Alexey :)

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

+1 > -Original Message- > From: Afek, Ifat (Nokia - IL/Kfar Sava) [mailto:ifat.a...@nokia.com] > Sent: Sunday, June 25, 2017 3:18 PM > To: OpenStack Development Mailing List (not for usage questions) > > Subject: Suspected SPAM - [openstack-dev]

Re: [openstack-dev] [vitrage] Gate issues

Hi, The gate problem was solved. The problem wasn’t with the setuptools, but with a change that was pushed to the project-config (a change that was also pushed to other projects configurations as well). Due to that problem the vitrage was enabled twice. BR, Alexey Weyl From: Yujun Zhang

Re: [openstack-dev] Suspected SPAM - Re: [vitrage] about  "is_admin" in ctx

at the moment will actually see all the entities. Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Wednesday, May 17, 2017 12:24 PM To: Weyl, Alexey (Nokia - IL/Kfar Sava) <alexey.w...@nokia.com> Cc: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev]Suspected SPA

Re: [openstack-dev] Suspected SPAM - Re: [vitrage] about  "is_admin" in ctx

is that although in the UI we have the admin tab for those users, the data we will show in the vitrage tab is not of all the tenants but this specific tenant. Alexey From: Weyl, Alexey (Nokia - IL/Kfar Sava) [mailto:alexey.w...@nokia.com] Sent: Tuesday, April 25, 2017 3:10 PM To: OpenStack Development

Re: [openstack-dev] [vitrage] about  "is_admin" in ctx

Hi Wenjuan, This is a good question, I need to check it a bit more thoroughly. It’s just that at the moment we are preparing for the Boston Openstack Summit and thus it will take me a bit more time to answer that. Sorry for the delay. Alexey ☺ From: dong.wenj...@zte.com.cn

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

Hi Dong, At the beginning that API was a mock, and then when the Vitrage started to work, we haven’t implemented the API and thus we can’t show an API in the client that doesn’t work. In order to implement that API it also needs to support Multi tenancy. Alexey From: dong.wenj...@zte.com.cn

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU]Re: [ALU]Re: [ALU][vitrage]how touseplaceholder vertex

ed "Cable", the other labeled "Wi-Fi"? -- Yujun On Mon, Jan 9, 2017 at 6:44 PM Weyl, Alexey (Nokia - IL) <alexey.w...@nokia.com> wrote: Hi Yujun, After some more checks, I found out the current code will handle your case as well, because it will go into the 2.c.1. Alexe

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU]Re: [ALU][vitrage]how touseplaceholder vertex

Hi Yujun, After some more checks, I found out the current code will handle your case as well, because it will go into the 2.c.1. Alexey > -Original Message- > From: Weyl, Alexey (Nokia - IL) [mailto:alexey.w...@nokia.com] > Sent: Monday, January 09, 2017 10:54 AM > T

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU][vitrage]how touseplaceholder vertex

: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU][vitrage]how touseplaceholder vertex Thanks Alexey. Could you explain a bit more detail based on the example in comments below? On Mon, Jan 9, 2017 at 4:08 PM Weyl, Alexey (Nokia - IL) <alexey.w...@nokia.com> wrote: That’s not what

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] Re: [ALU] Re: [ALU] [vitrage]how touseplaceholder vertex

To: OpenStack Development Mailing List (not for usage questions) Subject: [ALU] Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] Re: [ALU] [vitrage]how touseplaceholder vertex Hi, Alexey On Sun, Jan 8, 2017 at 2:50 PM Weyl, Alexey (Nokia - IL) <alexey.w...@nokia.com> wrote: Hi Yujun, A relati

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] Re: [ALU] [vitrage] how touseplaceholder vertex

Mailing List (not for usage questions) Subject: [ALU] Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] [vitrage] how touseplaceholder vertex A follow up question on relationships. On Thu, Jan 5, 2017 at 9:59 PM Weyl, Alexey (Nokia - IL) <alexey.w...@nokia.com> wrote: Hi Yujun, Lets s

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] [vitrage] how to useplaceholder vertex

s1 type: switch name: switch-1 id: 12345 state: available - config_id: h1 type: nova.host id: 1 relationships: - source: s1 target: h1 relation_type: attached On Wed, Dec 14, 2016 at 11:54 PM Weyl, Alexey (Nokia - IL) <alexey.w...@nokia.com>

Re: [openstack-dev] [ALU] [Vitrage] vitrage tempest job config

Bo problem Dong. If you have any more questions, don’t be shy, just ask. BR, Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Thursday, January 05, 2017 3:16 AM To: Weyl, Alexey (Nokia - IL) Cc: openstack-dev@lists.openstack.org Subject: 答复: RE: Re: [openstack-dev

Re: [openstack-dev] [ALU] [Vitrage] vitrage tempest job config

- name: osc-plugin-jobs Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Wednesday, January 04, 2017 10:59 AM To: Weyl, Alexey (Nokia - IL) Cc: openstack-dev@lists.openstack.org Subject: 答复: Re: [openstack-dev] [ALU] [Vitrage] vitrage tempest job config Hi Alexey, As far

Re: [openstack-dev] [ALU] [Vitrage] vitrage tempest job config

Hi Dong, All of that data is configured the openstack-infra/project-config in github. There you can find our changes by searching for vitrage. The main files that we have pushed our changes are: jenkins/jobs/vitrage.yaml gerrit/projects.yaml jenkins/jobs/projects.yaml BR, Alexey From:

Re: [openstack-dev] [Vitrage] [aodh] Generig alarm help

u.info] > Sent: Wednesday, December 21, 2016 5:20 PM > To: Weyl, Alexey (Nokia - IL) > Cc: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Vitrage] [aodh] Generig alarm help > > On Wed, Dec 21 2016, Weyl, Alexey (Nokia - IL) wro

[openstack-dev] [Vitrage] [aodh] Generig alarm help

Hi, I have pushed the first code of the generic alarm to the aodhclient. I encountered an error there in py27 which I don't quite understand why it happens because I have changed all the correct places in the client (maybe I need to have some appropriate code for this in the aodh project

Re: [openstack-dev] [ALU] Re: [ALU] [vitrage] how to use placeholder vertex

the static configuration. And the properties of `nova.host` resource shall to be merged from `static` and nova.host` datasources. Is that so? [1]: https://review.openstack.org/#/c/405354/   On Wed, Dec 14, 2016 at 5:40 PM Weyl, Alexey (Nokia - IL) <alexey.w...@nokia.com> wrote: Hi Yujun,   This is

Re: [openstack-dev] [ALU] [vitrage] how to use placeholder vertex

Hi Yujun, This is a good question, and let me explain for you how it works. Lets say we are supposed to get 2 entities from nova, nova.host called host1 and nova.instance called vm1 and vm1 is supposed to be connected to host1. The nova.host driver and nova.instance driver are working

Re: [openstack-dev] [Vitrage] [Aodh] Vitrage – Aodh Integration

Thanks, Alexey Weyl > -Original Message- > From: Julien Danjou [mailto:jul...@danjou.info] > Sent: Thursday, December 08, 2016 2:27 PM > To: Weyl, Alexey (Nokia - IL) > Cc: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Vitrage]

[openstack-dev] [Vitrage] [Aodh] Vitrage – Aodh Integration

Hi all, My name is Alexey Weyl and I am a core contributor in the Vitrage team. In the Austin Openstack summit we discussed with the Aodh team about creating a new alarm type, and after explaining it we got an approval [1]. Members from the Aodh team were in our design session in the Openstack

Re: [openstack-dev] [ALU] Re: [ALU] Re: [ALU] [vitrage] datasource driverreturnsentities only?

Sun, Dec 4, 2016 at 4:35 PM Weyl, Alexey (Nokia - IL) <alexey.w...@nokia.com<mailto:alexey.w...@nokia.com>> wrote: Hi Yujun, I see the confusion. The way we find the resource entity (it’s different than finding the alarm entity, but it’s ok because the static datasource is defining

Re: [openstack-dev] [ALU] Re: [ALU] [vitrage] datasource driver returnsentities only?

: nova.host name: host-2 id: 2 relation_type: attached On Thu, Dec 1, 2016 at 9:50 PM Weyl, Alexey (Nokia - IL) <alexey.w...@nokia.com<mailto:alexey.w...@nokia.com>> wrote: Hi Yujun, Get_all does returns a list of entities to be sent. Each event that is sent fro

Re: [openstack-dev] [ALU] [vitrage] datasource driver returns entities only?

Hi Yujun, Get_all does returns a list of entities to be sent. Each event that is sent from the driver to the processor contains also all the details of the neighbors that it connects to. For example, the event and data that we receive from nova about an instance also contains the host

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

Sounds good to me :) From: Afek, Ifat (Nokia - IL) [mailto:ifat.a...@nokia.com] Sent: Tuesday, November 29, 2016 11:23 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Suspected SPAM - Re: [openstack-dev] Suspected SPAM - [vitrage] datasources terminology Hi, A new

Re: [openstack-dev] [ALU] [vitrage] common vs utils

Sounds good to me ☺ From: Yujun Zhang [mailto:zhangyujun+...@gmail.com] Sent: Monday, November 28, 2016 10:43 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [ALU] [openstack-dev] [vitrage] common vs utils Currently, we have `common/utils.py`, `common/file_utils.py`

Re: [openstack-dev] [ALU] Re: [vitrage] about aodh alarm notification

ailto:zhang.yuj...@zte.com.cn>> 主题 Re: [openstack-dev] [vitrage] about aodh alarm notification Hi, Alexey My comments inline. On Mon, Nov 28, 2016 at 1:52 AM Weyl, Alexey (Nokia - IL) <alexey.w...@nokia.com<mailto:alexey.w...@nokia.com>> wrote: Hi Dong, I can think

Re: [openstack-dev] [vitrage] about aodh alarm notification

, November 25, 2016 2:28 AM To: Weyl, Alexey (Nokia - IL) Cc: Hefetz, Idan (Nokia - IL); Afek, Ifat (Nokia - IL); openstack-dev@lists.openstack.org; zhang.yuj...@zte.com.cn Subject: 答复: RE: RE: [openstack-dev] [vitrage] about aodh alarm notification EmThe solution goes back to my first question

Re: [openstack-dev] [vitrage] about aodh alarm notification

received, and each time we call the get_all of aodh (every snapshot_interval time) we can update the data in the cache as well. Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Thursday, November 24, 2016 11:24 AM To: Weyl, Alexey (Nokia - IL) Cc: Hefetz, Idan (Nokia - IL

Re: [openstack-dev] [vitrage] about aodh alarm notification

everything. If you have other questions, you are more than welcome to ask. Best Regrads, Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Thursday, November 24, 2016 9:39 AM To: Afek, Ifat (Nokia - IL); Weyl, Alexey (Nokia - IL); Hefetz, Idan (Nokia - IL); zhang.yuj

Re: [openstack-dev] [Vitrage] Problem at our gate in gerrit

gt; Subject: Re: [openstack-dev] [Vitrage] Problem at our gate in gerrit > > Thank you for your work! > > Best regards, > > Vinh Nguyen Trong > PODC - Fujitsu Vietnam Ltd. > Mobile: +84-164-953-8507 - Email: vin...@vn.fujitsu.com > > > -----Original Message- >

[openstack-dev] [Vitrage] Problem at our gate in gerrit

Hi, We have some problems at our gate in gerrit. We have fixed one problem by changing the image that the tempests run on to xenial image. But that has created some other problem, and we are checking it. I will send an email to update when the problem is resolved. Alexey

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

as earlier as possible. Each submit will be covered by additional unit test and keep backward compatibility. Detail replies inline. On Tue, Nov 15, 2016 at 5:51 PM Weyl, Alexey (Nokia - IL) <alexey.w...@nokia.com> wrote: Hi Yujun, Good job! This is a very important change for Vitrage.

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

Hi Yujun, Good job! This is a very important change for Vitrage. I have a couple of questions please: 1. Why do we want to create a new datasource ‘static’ and not rename the current ‘static_physical’ datasource and change it to work with the new format? 2. How are you planning to use the old

Re: [openstack-dev] [Vitrage] Installation

] Installation Hi Alexey, Yeap, it is what i mean. It seems that the connection channel between Zabbix and Vitrage just only through this script. Btw, thanks a lot Br, Tuan On Wed, Oct 5, 2016 at 3:37 PM, Weyl, Alexey (Nokia - IL) <alexey.w...@nokia.com<mailto:alexey.w...@nokia.com>&g

Re: [openstack-dev] [Vitrage] Installation

Hi, When you say notification in Zabbix, do you mean a new trigger in Zabbix? If yes, then if you have configured the auxiliary Zabbix script successfully then the script should recognize any trigger raised in zabbix and send the trigger notification on the oslo bus. Best Regards, Alexey

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

Hi Yujun, I don’t think we have a support for different versions of openstack at the same time at the moment. We have thought of such a requirement yet, but I think it can be done. If you can, please add a blueprint with all the details for such a feature. In addition, we now have a

Re: [openstack-dev] 答复: Re: 答复: [vitrage] can't get nagios datasource

: [vitrage] can't get nagios datasource Hi Alexey, There is a old vitrage.conf in my env, I didn't config Nagios in the datasources section. Is it can't be overwrited when i redeploy a new OS env? BR, dwj "Weyl, Alexey (Nokia - IL)" <alexey.w...@nokia.com<mailto:alexe

Re: [openstack-dev] 答复: [vitrage] can't get nagios datasource

Hi Dong, What was the problem? Alexey From: dong.wenj...@zte.com.cn [mailto:dong.wenj...@zte.com.cn] Sent: Monday, September 05, 2016 8:07 AM To: OpenStack Development Mailing List (not for usage questions) Cc: OpenStack Development Mailing List (not for usage questions) Subject:

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

typo when creating the template manually (I did this quite often...). My idea is to delegate the validation to datasource instead of enumerating all constants it in evaluator. I think this will introduce better extensibility. Any comments? On Thu, Aug 25, 2016 at 1:32 PM Weyl, Alexey (Nokia - IL)

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

Hi Yujun, You can find the names of the lables in the constants.py file. In addition, the restriction on the physical_static datasource is done in it’s driver.py. Alexey From: Yujun Zhang [mailto:zhangyujun+...@gmail.com] Sent: Thursday, August 25, 2016 4:50 AM To: OpenStack Development

Re: [openstack-dev] [vitrage] gate-vitrage-dsvm-api FAILURE

Hi Yujun, It seems to be due to changes that were made in other projects. We have the same problems with our commits. We are waiting to tomorrow to see it there will be any fixes in those projects for those problems. Alexey From: Yujun Zhang [mailto:zhangyujun+...@gmail.com] Sent: Friday,

Re: [openstack-dev] [nova] [vitrage] Nova host list api - performance

the content may result in great improvement in performance. -- Yujun On Mon, Aug 8, 2016 at 3:19 PM Weyl, Alexey (Nokia - IL) <alexey.w...@nokia.com<mailto:alexey.w...@nokia.com>> wrote: Hi, I am running the "client.hosts.list()" command in Vitrage to get all the hosts in t

[openstack-dev] [nova] [vitrage] Nova host list api - performance

Hi, I am running the "client.hosts.list()" command in Vitrage to get all the hosts in the system (we also run similar commands for availability zones and instances). Vitrage does this to gain a holistic view of system resources[1]. As part of our performance checks we noticed that when

[openstack-dev] [vitrage] Yaml file validation for Static Physical datasource

Hi Liat, I have noticed that you are working on the validation of the templates yaml files. Can you please write the validation for the static physical yaml files as well? Alexey __ OpenStack Development Mailing List (not

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

Sounds good Ifat and Eylon. Maybe we only need to think of a more general name for TERMINATING state (something that will include all end transient states). > -Original Message- > From: Afek, Ifat (Nokia - IL) [mailto:ifat.a...@nokia.com] > Sent: Monday, May 16, 2016 6:29 PM > To:

Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration

as OPNFV Doctor (that > wants events to happen in less than 1 second). > > Alexey > >> -Original Message- >> From: Weyl, Alexey (Nokia - IL) >> [mailto:alexey.w...@nokia.com<mailto:alexey.w...@nokia.com>] >> Sent: Tuesday, May 10, 2016 1:45 PM >

Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration

nal Message- > From: Weyl, Alexey (Nokia - IL) [mailto:alexey.w...@nokia.com] > Sent: Tuesday, May 10, 2016 1:45 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress > Collaboration > >

Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration

> To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress > Collaboration > > Hi Alexey, > > This use case sounds interesting. To be clarified it, I have a > question. > > On 2016/05/10 0:17, Weyl, Alexey (Nokia -

Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration

that policy. Here are the relevant docs. Datasource drivers http://docs.openstack.org/developer/congress/cloudservices.html Writing policy http://docs.openstack.org/developer/congress/policy.html Let me know if you have any questions, Tim On Wed, May 4, 2016 at 11:51 PM Weyl, Alexey (Nokia - IL

[openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration

Hi to all Vitrage and Congress contributors, We had a good introduction meeting in Austin and we (Vitrage) think that we can have a good collaboration between the projects. Vitrage, as an Openstack Root Cause Analysis (RCA) Engine, builds a topology graph of all the entities in the system

Re: [openstack-dev] [vitrage] [aodh] Error when creating 2 event alarms with the same name

, Weyl, Alexey (Nokia - IL) <alexey.w...@nokia.com<mailto:alexey.w...@nokia.com>> wrote: Hi, First of all, I wanted to thank again to all the participants in the fruitful Aodh-Vitrage design session in Austin :) I wanted to show in this email, the problem that we have when creating 2 e

Re: [openstack-dev] [vitrage] [aodh] Error when creating 2 event alarms with the same name

to:jul...@danjou.info] > Sent: Tuesday, May 03, 2016 6:03 PM > To: Weyl, Alexey (Nokia - IL) > Cc: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [vitrage] [aodh] Error when creating 2 > event alarms with the same name > > On Tue, May 03 2016, Weyl, Alexey (Nokia - IL)

[openstack-dev] [vitrage] [aodh] Error when creating 2 event alarms with the same name

Hi, First of all, I wanted to thank again to all the participants in the fruitful Aodh-Vitrage design session in Austin :) I wanted to show in this email, the problem that we have when creating 2 event alarms with the same name. Here is what I got in the command line:

Re: [openstack-dev] [vitrage] Cinder Datasource

sign you mentioned? By > datasource you mean the Cinder service? > There is already some work[1] to allow Cider to attach volumes in baremetal > servers. > > > [1] https://blueprints.launchpad.net/cinder/+spec/use-cinder-without-nova > > On Tue, Apr 12, 2016 at 4:02

Re: [openstack-dev] [telemetry][vitrage] Joint design sesssion in Austin

As far as Vitrage team is concerned, 16:10-16:50 works best for us, but we can attend either session if needed. Alexey Weyl -Original Message- From: Julien Danjou [mailto:jul...@danjou.info] Sent: Thursday, April 14, 2016 12:07 PM To: openstack-dev@lists.openstack.org Subject:

[openstack-dev] [vitrage] Change openstack.node to openstack.cluster

Hi, After some discussion, we have decided to change "openstack.node" to "openstack.cluster" as the "type" of the openstack cluster in the graph, to conform with the standard openstack terminology. Alexey __ OpenStack

[openstack-dev] [vitrage] Cinder Datasource

Hi, Here is the design of the Cinder datasource of Vitrage. Currently Cinder datasource is handling only Volumes. This datasource listens to cinder volumes notifications on the oslo bus, and updates the topology accordingly. Currently Cinder Volume can be attached only to instance (Cinder

[openstack-dev] [vitrage] Vitrage Demo - Alarms Use Case

Hi, We are happy to share with you all our second Vitrage demo, showing alarms imported from Nagios in Vitrage horizon UI. Here it is: https://www.youtube.com/watch?v=w1XQATkrdmg For more details about Vitrage, please visit our wiki here: https://wiki.openstack.org/wiki/Vitrage Thanks,

[openstack-dev] [vitrage] Vitrage Demo - Get Topology Use Case

Hi, We are happy to share with you all our first Vitrage demo, showing the "get topology" api and horizon UI. Here it is: https://www.youtube.com/watch?v=GyTnMw8stXQ=youtu.be For more details about Vitrage, please visit our wiki here: https://wiki.openstack.org/wiki/Vitrage Thanks, Alexey