Open Stack

Yep, +1 from me as well.  We've had good experiences with Kazoo. 


Devin Carlen


Founder, Chief Technology Officer


Nebula, Inc. | www.nebula.com (http://www.nebula.com/)


Cell: 206:883-5055



On Wednesday, May 1, 2013 at 2:05 PM, Joshua McKenty wrote:

> +1 for Kazoo, and I'm pretty sure @devcamcar would +1 this as well.
> 
> --
> Joshua McKenty, CTO
> Piston Cloud Computing, Inc.
> w: (650) 24-CLOUD
> m: (650) 283-6846
> http://www.pistoncloud.com
> 
> "Oh, Westley, we'll never survive!"
> "Nonsense. You're only saying that because no one ever has."
> 
> 
> 
> 
> On 2013-05-01, at 1:40 PM, Yun Mao wrote:
> > +1 on kazoo support. I was planning to do it but never got the bandwidth.
> > 
> > But I'd consider to add as another driver in addition to the python-evzookeeper based driver, instead of wiping out the existing one. We could phase out the old driver if kazoo offers better stability. 
> > 
> > Thanks,
> > 
> > Yun
> > 
> > 
> > 
> > On Wed, May 1, 2013 at 4:29 PM, Joshua Harlow <harlowja at yahoo-inc.com (mailto:harlowja at yahoo-inc.com)> wrote:
> > > Hi all, 
> > > 
> > > I was wondering if anyone had any strong feelings about moving from python-evzookeeper (https://pypi.python.org/pypi/evzookeeper/0.4.0) to kazoo (https://pypi.python.org/pypi/kazoo). 
> > > 
> > > Kazoo seems to be under a little more active development & maturity, and itself is pure-python (no dependence on a c-library and the associated issues with eventlet). 
> > > 
> > > I also like how kazoo has more of the recipes and primitives that will be useful going forward as the need for zookeeper gets bigger and bigger. 
> > > 
> > > Kazoo also seems to be in active use @ mozilla, zope, reddit and others, and has nice docs also @ http://kazoo.readthedocs.org/en/latest/ 
> > > 
> > > The only place right now that I see this attempt to use evzookeeper is in the servicegroup code, which I think can be ported to kazoo pretty easily. 
> > > 
> > > Would anyone have any strong feelings on that change? 
> > > 
> > > -Josh 
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > OpenStack-dev mailing list
> > > OpenStack-dev at lists.openstack.org (mailto:OpenStack-dev at lists.openstack.org)
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > > 
> > 
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org (mailto:OpenStack-dev at lists.openstack.org)
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org (mailto: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/20130501/004f5d0b/attachment.html>