Dynamically creating the secondary schedd config file and dirs
We currently have no good way to add or remove secondary schedds, after the initial install.
This ticket proposes a method for the config.d mode, where the assumption is that (with very few exceptions) the partial config files are never modified by hand.
The proposal is to create a tool that creates a dedicated config file, given the list of secondary collector names.
The same tool would also create directory trees needed for these schedds.
Any time the admin wants to change the list of secondary schedds, he just runs this tool and replaces to old config file.
Unused directory trees will not be touched, and existing ones will be reused.
#5 Updated by Igor Sfiligoi almost 8 years ago
OK, I guess I have to account for peoplw that like the '--help' option ;)
As it is, it does not recognize it, and thus assumes it is a schedd name.
Here is what you get if you run it without arguments, or with -h:
$ ./glidecondor_createSecSched Usage: glidecondor_createSecSched [-commonlog] [-nocreatedirs] <scheddlist> Example: glidecondor_createSecSched schedd_glideins1,schedd_glideins2
PS: Yes, we should put this in the manual (soon).
#6 Updated by John Weigand almost 8 years ago
No. My point was that the usage tells you nothing. It should tell you what all the args mean and what it is going to do, like what output it is creating and where. It is the first line of documentation and most times the only one an end user is going to look at. Finding it in our manual will be the last place anyone looks. My view.
#15 Updated by John Weigand over 7 years ago
- Status changed from Closed to Feedback
When you merged this into the master, I believe you forgot
to merge the doc