[openstack-dev] [oslo][kolla][openstack-helm][tripleo][all] Storing configuration options in etcd(?)
harlowja at fastmail.com
Wed Mar 15 05:08:20 UTC 2017
Monty Taylor wrote:
> On 03/14/2017 06:04 PM, Davanum Srinivas wrote:
>> 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.
> As I mentioned in the other thread, there was specific and strong
> anti-etcd sentiment in Tokyo which is why we decided to use an
> abstraction. I continue to be in favor of us having one known service in
> this space, but I do think that it's important to revisit that decision
> fully and in context of the concerns that were raised when we tried to
> pick one last time.
I'm in agreement with this.
I don't mind tooz either (it's good at what it is for) since I took a
part in creating it... Given that I can't help but wonder how nice it
would be to pick one (etcd, zookeeper, consul?) and just do nice things
with it (perhaps u know even work with the etcd or zookeeper or consul
developers [depending on which one we pick] on features and bug fixes
> It's worth noting that there is nothing particularly etcd-ish about
> storing config that couldn't also be done with zk and thus just be an
> additional api call or two added to Tooz with etcd and zk drivers for it.
Ya, to me zookeeper and etcd look pretty much the same now-a-days.
Which I guess is why https://github.com/coreos/zetcd ('A ZooKeeper
"personality" for etcd) (although I'm not sure I'd want to run that, ha)
exists as a thing.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev