Managing the configuration of server side applications as they make their way through multiple environments with multiple instances, elements of configuration that need to be secure or not, with the ability to see and understand what configuration a server is actually using at any particular time and manage that can be hard.
Some go for the easy route - just a text or xml file, some opt for a full revision control history solution which can have its own downsides. The big companies use ZooKeeper (Yahoo, Youtube, etc) or something else. But what about the NKOTB? etcd aims at solving the same problems, has a fairly simple API and is written in Go, so its deployment infrastructure is also fairly straightforward.
This session looks at distributed configuration management using etcd - how you populate it, how you watch it for changes, what you could and should do when it does change, atomicity of changes, implications of distributed configuration, sharing configuration so different environments see different config, sources of config, access control around populating configuration and other such topics.
Session is limited to 10, some of the participants have an agenda. End time is approximate.http://www.meetup.com/codelounge/events/218555612/