Read this first!
GlideinWMS RPMs are distributed via Open Science Grid (OSG) and documented in the following pages:
- Instructions to install via RPM the Frontend and the related components (User Collector, Submit host, ...)
- Instructions to install via RPM the Factory and related components (Factory collector)
These RPMs install a default version of the system but with the option to manually edit settings for more complicated configurations. Check the Factory configuration and Frontend configuration for a more detailed reference about the configuration.
TAR Files distribution is no longer supported. So for installation instructions see the RPM documents listed above amd hosted by OSG.
The following are recommended configurations for installing GlideinWMS. If you are installing a Factory, note that only configurations with the WMS Pool and Factory on the same node are supported. Also note that worker nodes must be able to access the web server on the Factory and Frontend nodes in order to download necessary files.
It should be noted that it is possible to install the GlideinWMS across administrative boundaries (i.e. you will only install part of the GlideinWMS infrastructure). See the OSG section below for an example.
Several possible configurations are:
Two Server configuration (recommended minimum):
- The GlideinWMS Pool and colocated glidein Factory node
- A node containing the Glidein Frontend, the glidein User Pool together with the scheduler for user submissions
Three Server configuration (recommended for 1000+ glideins)
- The glidein WMS Pool and colocated glidein Factory node
- A node containing the glidein User Pool together with the glidein Frontend
- A node containing the scheduler for user submissions
One Server configuration (Use only for test installs)
- The GlideinWMS Pool and colocated glidein Factory node, with the collector of the WMS Pool running on port 8618. Glidein Frontend, the glidein User Pool (collector running on default port 9618) together with the scheduler for user submissions. With this configuration, take special care of the ports assigned and of the condor.sh currently sourced when running commands.
See OSG Glidein Factory for more details on how to use this setup to talk to the OSG Factory. You will also need a proxy for the Frontend to communicate and (at least) one proxy for the glideins for submission.
OSG provides also an RPM to install the Glidein Frontend, the User Pool and scheduler. See the OSG GlideinWMS VO Frontend RPM installation guide for the RPM installation and configuration to use the OSG Factory. Note that the RPM installation by default installs all three these components.
- Quick Reference Guide to JWT Authentication Setup in GlideinWMS: for information on how to configure SciToken and IDToken security.
- Quick Reference Guide to GSI Authentication Setup in GlideinWMS: for information on how to configure the GSI security, and additional GSI configuration. GSI Authentication is being rapidly deprecated, please move to JWT authentication as soon as practicable.
- Multiple Schedds for increased scalability.
- Troubleshooting Frontend installation problems and Troubleshooting Factory installation problems.
- Frequently Asked Questions for advanced configuration tips.