<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px">Arg, sorry for the spam, mail.app was still trying to send it multiple times for some reason...<br><div id="yui_3_16_0_1_1415986513871_31756"><span></span></div><div id="yui_3_16_0_1_1415986513871_31757">-Josh</div><div id="yui_3_16_0_1_1415986513871_31758"><br></div><div id="yui_3_16_0_1_1415986513871_31759"> <br></div><div id="yui_3_16_0_1_1415986513871_31764" style="font-family: HelveticaNeue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div id="yui_3_16_0_1_1415986513871_31763" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div id="yui_3_16_0_1_1415986513871_31762" dir="ltr"> <hr size="1"> <font face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b> Joshua Harlow <harlowja@outlook.com><br> <b><span style="font-weight: bold;">To:</span></b> OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Friday, November 14, 2014 11:45 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [openstack-dev] [Heat] Using Job Queues for timeout ops<br> </font> </div> <div id="yui_3_16_0_1_1415986513871_31765" class="y_msg_container"><br>Sounds like this is tooz[1] ;)<br clear="none"><br clear="none">The api for tooz (soon to be an oslo library @ <a id="yui_3_16_0_1_1415986513871_31766" shape="rect" href="https://review.openstack.org/#/c/122439/" target="_blank">https://review.openstack.org/#/c/122439/</a>) 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.<br clear="none"><br clear="none"><a shape="rect" href="https://github.com/stackforge/tooz/blob/master/tooz/coordination.py#L63" target="_blank">https://github.com/stackforge/tooz/blob/master/tooz/coordination.py#L63</a><br clear="none"><br clear="none">CoordinationDriver<br clear="none">- watch_join_group<br clear="none">- unwatch_join_group<br clear="none">- join_group<br clear="none">- get_members<br clear="none">- ...<br clear="none"><br clear="none">Tooz has backends that use [redis, zookeeper, memcache] to achieve the above API (it also has some locking support for distributed locks as well).<br clear="none"><br clear="none">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).<br clear="none"><br clear="none">-josh<br clear="none"><div class="qtdSeparateBR"><br><br></div><div class="yqt8378809227" id="yqtfd76617"><br clear="none">On Nov 13, 2014, at 10:58 PM, Jastrzebski, Michal <<a shape="rect" ymailto="mailto:michal.jastrzebski@intel.com" href="mailto:michal.jastrzebski@intel.com">michal.jastrzebski@intel.com</a>> wrote:<br clear="none"><br clear="none">> 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.<br clear="none"><br clear="none"><br clear="none">_______________________________________________<br clear="none">OpenStack-dev mailing list<br clear="none"><a shape="rect" ymailto="mailto:OpenStack-dev@lists.openstack.org" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br clear="none"><a shape="rect" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br clear="none"></div><br><br></div> </div> </div> </div></body></html>