On Sep 1, 2011, at 06:08 , Andrew Hume wrote: > > think of this as a sort of survey. > > i am building a distributed cluster application which now has > two distinct sets of configuration info: > a) cluster-wide, shared by all components > b) server-specific, shared by components on a single server > for now, these are human-readable and editable text files > (NOT xml). the most likely changes to this information will be > A) tweaking of values for a new type of server (fair few over a day or > so) > B) cloning server2's config for server3 > > my question is: how would you prefer to arrange these in the file-system? > the two obvious answers are > 1) a single file (say config.all) with internal stanzas labelled by > server name > 2) two files, say config.clust and config.local. in this case, the > install process > would need to take the appropriate ref copy of config.server1 and install it > as > config.local on server1. > > what schemes have you liked best for this sort of thing? (and why?)
Is there a reason you're not embracing existing configuration management tools (CFEngine, Puppet, etc.). If that's overkill, I'd put all the config in network enabled VCS (git or similar), which should work well with your text-based config files, place copies of the repo on every station, then use a script to hard link the config file to it's working location (this way, if someone changes that config file directly in it's working dir, they're also changing the file in the repo). I'd organize based on server name or DNS information. - Zack -- Zack Williams - Artisan Computer Services - 520.867.8701 [email protected] http://www.artisancomputer.com Apple Certified System Administrator, Apple Consultants Network Microsoft Certified Professional, Small Business Specialist Sun Certified System Administrator Linux Professional Institute LPIC-1 _______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
