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?)
------------------
Andrew Hume (best -> Telework) +1 623-551-2845
[email protected] (Work) +1 973-236-2014
AT&T Labs - Research; member of USENIX and LOPSA
_______________________________________________
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/
