Open Stack

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?
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).

Regards,
Alex




From:   Xu He Jie <xuhj at linux.vnet.ibm.com>
To:     OpenStack Development Mailing List 
<openstack-dev at lists.openstack.org>, 
Date:   31/05/2013 03:46 PM
Subject:        [openstack-dev] Propose BP for Common Heartbeat Driver



Hi, guys,

I created a blueprint to create common heartbeat driver that can used by 
all the projects.
https://blueprints.launchpad.net/oslo/+spec/common-heartbeat-driver

The initial reason for creating this bp was quantum agent's heartbeat 
based on DB. That is inefficient
and not scalable.

We already have solution for same reason in nova servicegroup api and 
Matchmaker. So hope that can 
be merged as common module used by all the projects.

The common heartbeat driver should concern several problem as below:
* First... can be used by all the projects.
* Driver interface can support existed db based heartbeat for bw 
compatiblity.
* Working with Matchmaker that used by zmq rpc backend. Matchmaker will 
run heartbeat for each 
registered rpc consumer. Actually those heartbeat and agent/node heartbeat 
run in same process.
That is inefficient.

Before the bp reviewed and approved, I also submited WIP code for this. 
Hope that good for review bp
 and discussion. https://review.openstack.org/#/c/31048/1

Thanks.
Alex

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130602/556f2e18/attachment.html>