Arg, sorry for the spam, mail.app was still trying to send it multiple times
for some reason...
-Josh
From: Joshua Harlow <[email protected]>
To: OpenStack Development Mailing List (not for usage questions)
<[email protected]>
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.
https://github.com/stackforge/tooz/blob/master/tooz/coordination.py#L63
CoordinationDriver
- 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).
-josh
On Nov 13, 2014, at 10:58 PM, Jastrzebski, Michal
<[email protected]> 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
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
