Hi, I have a scenario for a small tomcat cluster; a setup where properties files are placed under version control, can get pushed out separately from code drops and can be changed separately from code drops (properties are managed in a cmdb, code in a vcs). There are multiple webapps, each with their own config (eg 4 app servers, 5 gateways, 3 seach nodes, ...) Fwiw, this setup isn't already using smartfrog to deploy the webapps.
I'm wondering if this is a good problem for smartfrog to solve, or if anyone here is doing something like this. I have fair idea what it can do for configurations of components but not for configuration inside components. I've been thinking about some alternate approaches, ranging from plain old scp, jmx, agents updating from central version control, push from distributed version control. All of which have specific problems, with two notable common ones; a) it'll end being a dedicated subsystem that only does properties config and yet another thing to manage, b) you have to think about what happens when the webapps are upgraded and possibly overwrite the properties files. Thoughts? cheers Bill ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Smartfrog-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/smartfrog-users
