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

Waines, Greg Greg.Waines at windriver.com
Tue May 16 13:36:45 UTC 2017


Two other more higher-level points I wanted to discuss with you about Masaraki.

so I notice that you are doing both monitoring, auto-recovery and even host maintenance
type functionality as part of the Masaraki architecture.

are you open to some configurability (enabling/disabling) of these capabilities ?

e.g. OPNFV guys would NOT want auto-recovery, they would prefer that fault events
                      get reported to Vitrage ... and eventually filter up to Aodh Alarms that get
                      received by VNFManagers which would be responsible for the recovery.

e.g. some deployers of openstack might want to disable parts or all of your monitoring,
         if using other mechanisms such as Zabbix or Nagios for the host monitoring (say)

are you open to configurably having fault events reported to Vitrage ?


From: Sam P <sam47priya at gmail.com>
Reply-To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Date: Monday, May 15, 2017 at 9:36 PM
To: "openstack-dev at lists.openstack.org" <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [vitrage] [nova] VM Heartbeat / Healthcheck Monitoring

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 monitor has similar functionality with what you
have described.
Please see [1] for more details on instance monitoring.
[0] https://wiki.openstack.org/wiki/Masakari
[1] https://github.com/openstack/masakari-monitors/tree/master/masakarimonitors/instancemonitor

Once masakari-monitors detect failures, it will send notifications to
masakari-api to take appropriate recovery actions to recover that VM
from failures.

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org<mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170516/73cff3dd/attachment.html>

More information about the OpenStack-dev mailing list