Setting up a gLite WMS
Notes for installing a gLite WMS on CentOS 3
About
The gLite Workload Management System is a replacement for the old LCG Resource Broker.
The current version is 2.4.4 (RPM glite-WMS-2.4.4) and it's installed with YAIM 3.1 on a CentOS 3 machine. A version for CentOS 4 is in the works.
Summary
The installation went smoothly, with only the 'boost' and 'boost-devel' packages needed from SLC. Some care was required because a dedicated 'glite' account will be created, with a default homedir of /home/glite.
Getting started
Installing the packages can be done with APT-RPM, a port of the Debian package manager to SL. It can be installed from http://glitesoft.cern.ch/scientific/30rolling/i386/apt-rpm/RPMS.os/apt-0.5.15cnc6-4.SL.i386.rpm
After installing APT, you need to configure several apt sources for various repositories:
- CentOS 3
- LCG-CA
- gLite-WMSLB
- JPackage 1.6
- SLC (ouch!)
the respective sources.lists are:
rpm http://linuxsoft.cern.ch/ LCG-CAs/current production rpm http://www.dutchgrid.nl/mirror/apt/centos 3/i386 os updates rpm http://glitesoft.cern.ch/EGEE/gLite/APT/R3.0/glite-WMSLB rhel30 externals Release3.0 updates rpm http://www.dutchgrid.nl/mirror/jpackage 1.6/generic free rpm http://www.dutchgrid.nl/mirror/jpackage 1.6/redhat-el-3.0 free rpm http://linuxsoft.cern.ch cern/slc30X/i386/apt os updates extras
doing an
apt-get update && apt-get install lcg-CA && apt-get install glite-WMSLB
after that should install the middleware. This will pull in glite-yaim-core, glite-yaim-lb and glite-yaim-wms as well.
The list of installed packages.
Configuring the middleware
Install the host cert and key, prepare gridmapdir and such. Install the VOMS server cert in /etc/grid-security/vomsdir.
Using YAIM, the configuration can be done provided a good site-info.def file is prepared. The yaim command line then is:
/opt/glite/yaim/bin/yaim -c -s site-info.def -n glite-WMS -n glite-LB
A dedicated account for glite is being made (config_edgusers). The host key and cert are copied to ~glite/.certs. The default location is /home/glite and if you don't like that set
GLITE_USER_HOME=/preferred/glite/home/dir
in site-info.def. Make sure gridmapdir is writable by glite.
A bug in yaim (GGUS ticket 27609) hardcodes /home/glite (scripts config_glite_lb and config_glite_lbproxy) for GLITE_HOST_CERT and GLITE_HOST_KEY.
Usage hints
The UI commands for job submission all start with glite-wms-. These are similar to the good old edg- commands, with some slight differences. In fact, you could probably get away with the following aliases:
alias edg-job-list-match='glite-wms-job-list-match -a' alias edg-job-submit='glite-wms-job-submit -a' alias edg-job-status='glite-wms-job-status' alias edg-job-get-logging-info='glite-wms-job-get-logging-info' alias edg-job-cancel='glite-wms-job-cancel' alias edg-job-get-output='glite-wms-job-output'
A subtle difference with retrieving output is the --dir option; the edg tools would create a unique subdirectory in the given directory, so --dir=. would work nicely. But the new tools drop the output directly in the given directory. Using --dir=. results in a warning that the directory already exists.
The preferred form of proxy delegation is by using glite-wms-job-delegate-proxy:
glite-wms-job-delegate-proxy -d <my_favorite_handle>
and subsequently referring to the handle in the other commands:
glite-wms-job-submit -d <my_handle> <jdl_file>
Links
- gLite WMS troubleshooting guide
- https://twiki.cern.ch/twiki/bin/view/LCG/GLiteWMSTroubleshooting
- gLite WMS release notes
- https://twiki.cern.ch/twiki/bin/view/EGEE/Glite30WMSCHKPTProd
- Generic installation guide
- https://twiki.cern.ch/twiki/bin/view/LCG/GenericInstallGuide301
- YAIM guide
- https://twiki.cern.ch/twiki/bin/view/LCG/YaimGuide311