SImple configurator for RPM installs
The current RPM installation of glideinWMS requires the user
to manually modify the condor_config and frontend.xml files
and also create the condor_mapfile.
The initial config files (condor/frontend) are hard-coded for
the UCSD factory. If a user is going to use the RPM
installation with a non-UCSD factory, the changes required are
A simple configurator would make life easy and reduce the
likelihood of errors. It would also make life easier for
testing locally where non-UCSD factories are used.
#1 Updated by John Weigand about 8 years ago
Below is a sortof prototype for more easily configuring an
RPM installed glideinwms frontend.
Give me a call when anyone wants to try it and I will talk you
through it. The rpm.conf is the driver. It is not an ini
file just a 2 token file similar to a condor_config.
My thoughts in the longer run are to use templates like the
*.template files you see for the ini installer thus
making tarball and rpm based installations similar and
easier to maintain from a development standpoint.
config.py is the configurator.
On another note: I noticed that the ./install/glidecondor_addDN
module that Igor created allowing a user to more easily add DN's
to the condor_mapfile with the proper syntax is missing from the
RPM installation. I think this is something that should be added.