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

2016-05-16 Thread Weyl, Alexey (Nokia - IL)
: [openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration Hi Alexey, That sounds like a good use case. If I understand it correctly, the use case can be accomplished by doing two things: 1. Writing a Vitrage datasource driver that whenever it receives an alarm, pulls Vitrage's API.

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

2016-05-12 Thread Tim Hinrichs
less than 1 second). > > > > Alexey > > > >> -Original 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

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

2016-05-12 Thread Masahito MUROI
- 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 Hi Masahito, Thanks for your question. There are two main reasons why we ne

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

2016-05-10 Thread Weyl, Alexey (Nokia - IL)
Original 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

2016-05-10 Thread Weyl, Alexey (Nokia - IL)
> 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 - IL

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

2016-05-10 Thread Masahito MUROI
questions) *Subject:* Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration Hi Alexey, Thanks for the overview of how you see a Congress-Vitrage integration being valuable. I'd imagine that the right first step in this integration would be creating a new datasource driver w

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

2016-05-09 Thread Weyl, Alexey (Nokia - IL)
) Subject: Re: [openstack-dev] [vitrage] [congress] Vitrage-Congress Collaboration Hi Alexey, Thanks for the overview of how you see a Congress-Vitrage integration being valuable. I'd imagine that the right first step in this integration would be creating a new datasource driver within Congress to

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

2016-05-06 Thread Tim Hinrichs
Hi Alexey, Thanks for the overview of how you see a Congress-Vitrage integration being valuable. I'd imagine that the right first step in this integration would be creating a new datasource driver within Congress to pull data from Vitrage. It doesn't need to pull all the data in your list to sta

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

2016-05-04 Thread Weyl, Alexey (Nokia - IL)
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 (phys