
----- Original Message -----
From: "Gilad Chaplik" <gchaplik@redhat.com> To: "Yair Zaslavsky" <yzaslavs@redhat.com> Cc: "Arthur Berezin" <aberezin@redhat.com>, "users" <users@ovirt.org> Sent: Monday, May 5, 2014 10:57:01 AM Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" - feature pages
----- Original Message -----
From: "Yair Zaslavsky" <yzaslavs@redhat.com> To: "Arthur Berezin" <aberezin@redhat.com> Cc: "Gilad Chaplik" <gchaplik@redhat.com>, "users" <users@ovirt.org> Sent: Monday, May 5, 2014 6:39:02 AM Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" - feature pages
----- Original Message -----
From: "Arthur Berezin" <aberezin@redhat.com> To: "Gilad Chaplik" <gchaplik@redhat.com> Cc: "users" <users@ovirt.org> Sent: Sunday, May 4, 2014 5:35:59 PM Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" - feature pages
In this case engine periodically checks health of hosts' power management as HA relies on it.
Arthur
----- Original Message -----
From: "Gilad Chaplik" <gchaplik@redhat.com> To: "Eli Mesika" <emesika@redhat.com> Cc: "users" <users@ovirt.org>, "Arthur Berezin" <aberezin@redhat.com> Sent: Sunday, May 4, 2014 5:26:45 PM Subject: Re: [ovirt-users] oVirt 3.5 : "Power Management Health Check" - feature pages
Hi Eli,
Here is my comment :) Why engine needs to send the status health check, isn't there any 3rd parties that does it, that we can integrate with? If found, it probably has /less (known) bugs/more features/ and it's already written, tested, documented, allows further integration and probably deals with scale.
btw, fixed some typos in your pages :-)
Thanks, Gilad.
Hi, what 3rd party for example do you refer to? The PM code already exists at engine, And you're also using quartz for scheduling.
Yair,
You're are raising some good points, but imo the entire host monitoring (inc getVdsStats, etc.) should be externalized. There are 2 major issues that we still don't cover: - No HA for monitoring, who checks the hosts when the engine is down. - No scale - the engine is a bottle-neck in network and compute. Although the above is a huge arch change, we need to start somewhere, this feature sounds like a candidate to introduce it.
About the examples: http://sixrevisions.com/tools/10-free-server-network-monitoring-tools-that-k... The main goal of the feature if my suggestion is taken, is to select to most appropriate one.
Thanks, Gilad.
Well, Nagios is being considered to be used or used by Gluster guys. However, it will still require (AFAIK) to code some nagios plugin to perfrom the health check. In addition, you will have to report somehow the state change to engine. IMHO, this a bit of an overkill (look also at the time that the check is run - once in an hour, so it can't be compared to getVmStats).
----- Original Message -----
From: "Eli Mesika" <emesika@redhat.com> To: "users" <users@ovirt.org> Cc: "Arthur Berezin" <aberezin@redhat.com> Sent: Sunday, May 4, 2014 12:18:47 PM Subject: [ovirt-users] oVirt 3.5 : "Power Management Health Check" - feature pages
Hi
The following wiki pages were added to the "Power Management Health Check" feature planned for oVirt 3.5
http://www.ovirt.org/Features/PMHealthCheck http://www.ovirt.org/Features/Design/DetailedPMHealthCheck
Your comments/questions are mostly welcomed.
Thanks Eli Mesika _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users