So just out of curiosity, but do people really even know what etcd is good for? I am thinking that there should be some guidance from folks in the community as to where etcd should be used and where it shouldn't (otherwise we just all end up in a mess).

Perhaps a good idea to actually give examples of how it should be used, how it shouldn't be used, what it offers, what it doesn't... Or at least provide links for people to read up on this.


Davanum Srinivas wrote:
One clarification: Since just
uses the HTTP API (/v3alpha) it will work under both eventlet and
non-eventlet environments.


On Wed, Jun 7, 2017 at 6:47 AM, Davanum Srinivas<>  wrote:

Here's the update to the base services resolution from the TC:

First request is to Distros, Packagers, Deployers, anyone who
installs/configures OpenStack:
Please make sure you have latest etcd 3.x available in your
environment for Services to use, Fedora already does, we need help in
making sure all distros and architectures are covered.

Any project who want to use etcd v3 API via grpc, please use: (works only for non-eventlet services)

Those that depend on eventlet, please use the etcd3 v3alpha HTTP API using:

If you use tooz, there are 2 driver choices for you:

If you use oslo.cache, there is a driver for you:

Devstack installs etcd3 by default and points cinder to it:

Review in progress for keystone to use etcd3 for caching:

Doug is working on proposal(s) for oslo.config to store some
configuration in etcd3:

So, feel free to turn on / test with etcd3 and report issues.


Davanum Srinivas ::

OpenStack Development Mailing List (not for usage questions)

Reply via email to