[openstack-dev] [Heat] Locking and ZooKeeper - a space oddysey

Sandy Walsh sandy.walsh at rackspace.com
Wed Oct 30 20:05:57 UTC 2013



On 10/30/2013 04:44 PM, Robert Collins wrote:
> On 31 October 2013 08:37, Sandy Walsh <sandy.walsh at rackspace.com> wrote:
>> Doh, sorry, left out the important part I had originally intended.
>>
>> The ZK unit tests could be split to not run by default, but if you're a
>> ZK shop ... run them yourself. They might not be included in the gerrit
>> tests, but should be the nature with heavy-weight drivers.
>>
>> We need to do more of this test splitting in general anyway.
> 
> Yes... but.
> 
> We need to aim at production. If ZK is going to be the production sane
> way of doing it with the reference OpenStack code base, then we
> absolutely have to have our functional and integration tests run with
> ZK. Unit tests shouldn't be talking to a live ZK anyhow, so they don't
> concern me.

Totally agree at the functional/integration test level. My concern was
having to bring ZK into a dev env.

We've already set the precedent with Erlang (rabbitmq). There are HBase
(Java) drivers out there and Torpedo tests against a variety of other
databases.

I think the horse has left the barn.


> 
> -Rob
> 



More information about the OpenStack-dev mailing list