Open Stack

Good idea, phased approach might help.

I'll see if I can get a person here to help with this.

From: Yun Mao <yunmao at gmail.com<mailto:yunmao at gmail.com>>
Reply-To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Wednesday, May 1, 2013 1:40 PM
To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] Move from evzookeeper to kazoo?

+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


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