I've done this before with puppet, but any sort of mainstream
configuration management system should work. There will be some
management overhead in making sure any token changes make it back into
the right server-specific template, but otherwise it's straight
forward.
On Thu, Dec 30, 2010 at 2:56
You can specify the location of cassandra.yaml with a url so you can keep
your configs in one (redundant place) like S3 or generate them on the fly in
a http service...
On Thu, Dec 30, 2010 at 3:34 PM, B. Todd Burruss wrote:
> how are folks customizing the cassandra.yaml for each node in the c
Funny you should mention that. I just put my half-baked solution to
this problem on github today.
https://github.com/gdusbabek/cassandra-maker. It generates
cassandra.yaml files (and entire config directories too) that are
based on the svn defaults. It should be easy to customize it to fit
your
