Comment 25 for bug 1375625

Ah ha, that's a whole different discussion. There's currently an RFE bug floating around for Neutron adopting Tooz for its locking API (https://bugs.launchpad.net/neutron/+bug/1552680). There's critical questions yet resolved in the wider OpenStack context: Can a core project like Neutron assume that a Tooz backend is available in any OpenStack deployment? How does packaging / downstream consumption look like for Tooz backends? Does the API sufficiently hide the differences between Tooz's backends (It doesn't) so that users (Neutron) can be agnostic of redis/etcd/zookeeper implementation details / bugs / workarounds?

I'm trying to say that I'm not convinced in our ability to adopt Tooz in the short term in the OpenStack context, but we will see :)