9ad8f55ce8
There have been a lot of discussions around scenarios like distributed locks, storing additional configuration information and coordinating service liveness checks without using a database etc. Example: http://lists.openstack.org/pipermail/openstack-dev/2015-November/thread.html#78214 http://lists.openstack.org/pipermail/openstack-dev/2017-March/thread.html#113941 http://lists.openstack.org/pipermail/openstack-dev/2017-March/thread.html#113885 So at the Boston Summit Forum, we had a session on a specific proposal to consider Etcd 3.x for such scenarios: https://etherpad.openstack.org/p/BOS-etcd-base-service There was consensus in the room based on which a bunch of work was done in tooz, devstack etc after thorough research on the options available for both eventlet and non-eventlet based services. The consensus grew around folks using oslo library like tooz or if they choose, they can directly use etcd using python client libraries like etcd3 (for non-eventlet scenarios) and etcd3gw (for eventlet based scenarios). We should be using the v3 APIs using the etcd 3.1.x versions to avoid migration issues from the older v2 APIs. Change-Id: Id6dd2a8fffd50dca8f0de05def20d31bf9c61717
This repository contains OpenStack Technical Committee reference documents and tracks official resolutions voted by the committee.
Directory structure:
- reference/
Reference documents which need to be revised over time. Some motions will just directly result in reference doc changes.
- resolutions/
When the motion does not result in a change in a reference doc, it can be expressed as a resolution. Those must be named YYYYMMDD-short-name with YYYYMMDD being the proposal date in order to allow basic sorting.
- goals/
Documentation for OpenStack community-wide goals, organized by release cycle. These pages will be updated with project status info over time, and if goals are revised.
See https://wiki.openstack.org/wiki/Governance/TechnicalCommittee for details.