Configuration Management


#1

I’m looking at ways to improve the way we do config management.

I know Chef is very good at managing deploy time OS and env config, however,
when it comes to app/code config it gets a bit tricky as there are various
levels of config: build vs deploy vs runtime/dynamic.

For dynamic/runtime config I’m thinking about tools like Zookeeper, but I’m
also keen on using feature toggles that have their own config (similar to
Togglz framework).

Ideally, I would like to not manage config in multiple places, but have one
place where all the tools (Chef, Zookeeper and Togglz) can pull the config from
(or have it pushed from that central place).

Any ideas how to approach something like this with Chef?

Thanks,
Florin Dragu


#2

On Monday, August 26, 2013 at 11:42 AM, florin.dragu@nike.com wrote:

I’m looking at ways to improve the way we do config management.

I know Chef is very good at managing deploy time OS and env config, however,
when it comes to app/code config it gets a bit tricky as there are various
levels of config: build vs deploy vs runtime/dynamic.

For dynamic/runtime config I’m thinking about tools like Zookeeper, but I’m
also keen on using feature toggles that have their own config (similar to
Togglz framework).

What kind of config are you changing at runtime, and how frequently? How quickly do you need the change to propagate? Is this something that requires you to restart/HUP the app, or does the app read it directly?


Daniel DeLeo