[openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)
harlowja at fastmail.com
Tue Mar 14 23:05:02 UTC 2017
So just fyi, this has been talked about before (but prob in context of
zookeeper or various other pluggable config backends).
I think the general questions that seem to reappear are around the
* How does reloading work (does it)?
* What's the operational experience (editing a ini file is about the
lowest bar we can possible get to, for better and/or worse).
* Does this need to be a new oslo.config backend or is it better suited
by something like the following (external programs loop)::
etcd_client = make_etcd_client(args)
has_changed = etcd_client.get_new_config("/blahblah") # or use a
* Is an external loop better (maybe, maybe not?)
Pretty sure there are some etherpad discussions around this also somewhere.
Clint Byrum wrote:
> Excerpts from Davanum Srinivas's message of 2017-03-14 13:04:37 -0400:
>> So one more thing popped up again on IRC:
>> What do you think? interested in this work?
>> PS: Between this thread and the other one about Tooz/DLM and
>> os-lively, we can probably make a good case to add etcd as a base
>> always-on service.
> This is a cool idea, and I think we should do it.
> A few loose ends I'd like to see in a spec:
> * Security Security Security. (Hoping if I say it 3 times a real
> security person will appear and ask the hard questions).
> * Explain clearly how operators would inspect, edit, and diff their
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev