<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2013年06月03日 00:41, Alex Glikson
wrote:<br>
</div>
<blockquote
cite="mid:OF0DEE1498.CC19C080-ONC2257B7E.005AB6D3-C2257B7E.005BB7C5@il.ibm.com"
type="cite"><font face="sans-serif" size="2">If the goal is
heartbeat of OpenStack services (such as nova-compute,
cinder-volume, etc) -- then servicegroup is designed to do
exactly that (for historical reasons the name is a bit more
generic -- implying that it can eventually support additional
group communication functions for services). Is there anything
in particular you see missing in it?</font> <br>
</blockquote>
Yes, the goal is heartbeat of openstack services.<br>
<blockquote
cite="mid:OF0DEE1498.CC19C080-ONC2257B7E.005AB6D3-C2257B7E.005BB7C5@il.ibm.com"
type="cite"><font face="sans-serif" size="2">BTW, a more generic
heartbeat abstraction might be useful for scenarios like VM HA,
where in addition to monitoring individual services it could
make sense to monitor the liveness of physical nodes in a more
holistic way (e.g., think of Linux-HA heartbeat/coresync as a
backend driver)</font> </blockquote>
Does 'VM HA' means the physical nodes that running the VMs is down,
then nova should startup those VMs on another physical nodes?<br>
<br>
What I understand was there are two layers of HA:<br>
1.The HA of physical node was done by heartbeat/corosync+pacemaker,
as this describe
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="http://docs.openstack.org/trunk/openstack-ha/content/ch-intro.html">http://docs.openstack.org/trunk/openstack-ha/content/ch-intro.html</a><br>
2.The HA of service that provided by openstack was done by this
common heartbeat driver(<font face="sans-serif" size="2">to
monitoring individual services</font>).<br>
<br>
The VM(compute service) provided by nova. So VM HA should be done by
this common heartbeat driver, it needn't monitor liveness of
physical nodes in heartbeat driver.<br>
Does make sense?<br>
<br>
I agree with you the heartbeat abstraction should be generic, then
it can be used by more scenarios. I have written the document about
the abstraction: <br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="https://docs.google.com/document/d/1IClo_8OxG8b7bT9zcVdO5rIqucR6ZYq3yFhIj7UJIeA/edit#heading=h.2f5wiqa9s5j3">https://docs.google.com/document/d/1IClo_8OxG8b7bT9zcVdO5rIqucR6ZYq3yFhIj7UJIeA/edit#heading=h.2f5wiqa9s5j3</a><br>
And there is a WIP patch:
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://review.openstack.org/#/c/31048/">https://review.openstack.org/#/c/31048/</a><br>
<br>
Welcome any comment!<br>
<br>
Thanks.<br>
<blockquote
cite="mid:OF0DEE1498.CC19C080-ONC2257B7E.005AB6D3-C2257B7E.005BB7C5@il.ibm.com"
type="cite"><font face="sans-serif" size="2"><br>
Regards,</font> <br>
<font face="sans-serif" size="2">Alex</font> <br>
<br>
<br>
<br>
<br>
<font face="sans-serif" size="1" color="#5f5f5f">From: </font><font
face="sans-serif" size="1">Xu He Jie <a
class="moz-txt-link-rfc2396E"
href="mailto:xuhj@linux.vnet.ibm.com"><xuhj@linux.vnet.ibm.com></a></font>
<br>
<font face="sans-serif" size="1" color="#5f5f5f">To: </font><font
face="sans-serif" size="1">OpenStack Development Mailing List <a
class="moz-txt-link-rfc2396E"
href="mailto:openstack-dev@lists.openstack.org"><openstack-dev@lists.openstack.org></a>,
</font> <br>
<font face="sans-serif" size="1" color="#5f5f5f">Date: </font><font
face="sans-serif" size="1">31/05/2013 03:46 PM</font> <br>
<font face="sans-serif" size="1" color="#5f5f5f">Subject: </font><font
face="sans-serif" size="1">[openstack-dev] Propose BP for Common
Heartbeat Driver</font> <br>
<hr noshade="noshade"> <br>
<br>
<br>
<font size="3">Hi, guys,<br>
<br>
I created a blueprint to create common heartbeat driver that can
used by all the projects.</font><font size="3" color="blue"><u><br>
</u></font><a moz-do-not-send="true"
href="https://blueprints.launchpad.net/oslo/+spec/common-heartbeat-driver"><font
size="3" color="blue"><u>https://blueprints.launchpad.net/oslo/+spec/common-heartbeat-driver</u></font></a><font
size="3"><br>
<br>
The initial reason for creating this bp was quantum agent's
heartbeat based on DB. That is inefficient<br>
and not scalable.<br>
<br>
We already have solution for same reason in nova servicegroup
api and Matchmaker. So hope that can <br>
be merged as common module used by all the projects.<br>
<br>
The common heartbeat driver should concern several problem as
below:<br>
* First... can be used by all the projects.<br>
* Driver interface can support existed db based heartbeat for bw
compatiblity.<br>
* Working with Matchmaker that used by zmq rpc backend.
Matchmaker will run heartbeat for each <br>
registered rpc consumer. Actually those heartbeat and agent/node
heartbeat run in same process.<br>
That is inefficient.<br>
<br>
Before the bp reviewed and approved, I also submited WIP code
for this. Hope that good for review bp<br>
and discussion. </font><a moz-do-not-send="true"
href="https://review.openstack.org/#/c/31048/1"><font size="3"
color="blue"><u>https://review.openstack.org/#/c/31048/1</u></font></a><font
size="3"><br>
<br>
Thanks.<br>
Alex<br>
<br>
</font><tt><font size="2">_______________________________________________<br>
OpenStack-dev mailing list<br>
<a class="moz-txt-link-abbreviated"
href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
</font></tt><a moz-do-not-send="true"
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"><tt><font
size="2">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></tt></a><tt><font
size="2"><br>
</font></tt> <br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>