[openstack-dev] [Heat] Using Job Queues for timeout ops

Joshua Harlow harlowja at yahoo-inc.com
Fri Nov 14 20:03:15 UTC 2014

Arg, sorry for the spam, mail.app was still trying to send it multiple times for some reason...
     From: Joshua Harlow <harlowja at outlook.com>
 To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org> 
 Sent: Friday, November 14, 2014 11:45 AM
 Subject: Re: [openstack-dev] [Heat] Using Job Queues for timeout ops
Sounds like this is tooz[1] ;)

The api for tooz (soon to be an oslo library @ https://review.openstack.org/#/c/122439/) is around coordination and 'service-group' like behavior so I hope we don't have duplicates of this in 'oslo.healthcheck' instead of just using/contributing to tooz instead.


- watch_join_group
- unwatch_join_group
- join_group
- get_members
- ...

Tooz has backends that use [redis, zookeeper, memcache] to achieve the above API (it also has some locking support for distributed locks as well).

Feel free to jump on #openstack-state-management if u want more info (jd and the enovance guys and myself have developed that library for this kind of purpose).


On Nov 13, 2014, at 10:58 PM, Jastrzebski, Michal <michal.jastrzebski at intel.com> wrote:

> Also, on "Common approach to HA" session we moved something like oslo.healthcheck (or whatever it will be called), common lib for service-group like behavior. In my opinion it's pointless to implement zookeeper management in every project separately (its already in nova..). Might be worth looking closely into this topic.

OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141114/0514cda2/attachment.html>

More information about the OpenStack-dev mailing list