[openstack-dev] [Monasca][vitrage] Vitrage project

AFEK, Ifat (Ifat) ifat.afek at alcatel-lucent.com
Mon Dec 7 09:38:01 UTC 2015

Hi Roland,

We created a blueprint for Vitrage-Monasca integration: 
We will be happy to get your comments about it.


> -----Original Message-----
> From: Hochmuth, Roland M [mailto:roland.hochmuth at hpe.com]
> Sent: Thursday, November 19, 2015 8:51 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Monasca][vitrage] Vitrage project
> Hi Ifat, Thanks for the heads-up. We will start reviewing your
> blueprints and providing feedback.
> With respect to the support for AODH, I'm assuming that you are
> referring too,
> https://review.openstack.org/#/c/244049/2/specs/mitaka/manage-
> ceilometer-al
> arms.rst. For adding support for Monasca, a Vitrage Notifier would be
> developed for Monasca.
> In the diagram at, https://wiki.openstack.org/wiki/Vitrage, it shows
> the Synchronizer collecting data, such as OpenStack notifications,
> which usually implies RabbitMQ. With the Ceilosca effort,
> https://www.openstack.org/summit/tokyo-
> 2015/videos/presentation/ceilometer-
> monascaceilosca and https://github.com/openstack/monasca-ceilometer, we
> are planning on sending OpenStack Notifications from Ceilometer to
> Monasca. Monasca will then publish to the Kafka queue. Would you be
> interested in consuming events from Kafka by the Synchronizer to reduce
> the load on RabbitMQ?
> In the use cases you discuss getting health/status information about a
> switch and correlating problems to VMs. But, in the diagram only SDN
> Controller, Heat, Cinder and Nova are shown. Are you planning on
> receiving health/status information from other sources? Monasca is
> processing metrics for many components, such as the physical
> infrastructure used for running the cloud and for OpenStack resources,
> and generating alarms. For example, in your use case, Monasca could be
> monitoring the physical switch and creating alarms. Should alarms that
> Monasca creates be a source for the Vitrage Synchronizer?
> Regards --Roland
> On 11/17/15, 3:02 AM, "AFEK, Ifat (Ifat)" <ifat.afek at alcatel-
> lucent.com>
> wrote:
> >Hi Monasca developers,
> >
> >As you might have heard in Mitaka Summit, we have started a new
> project
> >named Vitrage[1]. We would like it to be the Openstack RCA (Root Cause
> >Analysis) Engine for organizing, analyzing and expanding OpenStack
> >alarms & events, yielding insights regarding the root cause of
> problems
> >and deducing the existence of problems before they are directly
> detected.
> >
> >We are now in the process of reviewing the blueprints[2] that we wish
> >to implement in mitaka. At the first stage of the implementation we
> >plan to integrate with AODH alarms. In the next phase, we would like
> to
> >check how we can integrate with Monasca as well. We would be happy to
> >get your reviews for our blueprints, to make sure our architecture
> >matches this future integration.
> >
> >Your feedback would be highly appreciated.
> >
> >[1] https://wiki.openstack.org/wiki/Vitrage
> >[2] https://blueprints.launchpad.net/vitrage
> >
> >Thanks,
> >Ifat Afek.
> >
> >
> >
> >______________________________________________________________________
> _
> >___ OpenStack Development Mailing List (not for usage questions)
> >Unsubscribe:
> >OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> _______________________________________________________________________
> ___
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-
> request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list