Installation Process
Installation of glideinWMS is a multi-step process:
- Components and Pre-requisites: Includes a consolidated table of requirements for each server.
- The glidein WMS Collector and collocated glidein Factory node
- The glidein pool Collector node
- One or more scheduler nodes for user submission
- The Glidein Frontend
The above process should suffice for typical installs. More information can be found below.
Additional Documents:
- Component Installation: Installation tips for components needed by glideinWMS, such as HTTP, VDT, JavascriptRRD, etc.
- Installation of a GCB node: (only if
you are gliding into Grid sites with restrictive network policies
and cannot use CCB)
NOTE: It is strongly recommended to use CCB over GCB if possible. - Quick Reference Guide to GSI Authentication Setup in glideinWMS: for information on how to configure the GSI security, and additional GSI configuration.
- Multiple Schedds for increased scalability.
- Quill setup for older condor installs.
- Troubleshooting Frontend installation problems and Troubleshooting Factory installation problems.
- Frequently Asked Questions for advanced configuration tips.
Possible Configurations
While the documents presented here assume you will install each component on a different machine, there is nothing preventing you from installing all of them on fewer machines, or even on one machine only (excluding GCB, but you should not use it anyhow). Note that only configurations with the WMS collector and factory on the same node are supported. Also note that worker nodes must be able to access the web server on the factory node in order to download neccessary 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 below:
Two Server configuration (recommended minimum):
- The glidein WMS Collector and collocated glidein Factory node
- A node containing the Glidein Frontend, the glidein pool Collector together with the scheduler for user submissions
Three Server configuration (recommended for 1000+ glideins)
- The glidein WMS Collector and collocated glidein Factory node
- A node containing the glidein pool Collector together with the VO Frontend
- A node containing the scheduler for user submissions
One Server configuration (Use only for test installs)
- The glidein WMS Collector and collocated glidein Factory node, with the collector running on 8618. Glidein Frontend, the glidein pool Collector (running on 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.
Members of the Open Science Grid can use the OSG factory at UCSD. In this case, only the following installation is necessary:
See OSG Glidein Factory for more details on how to use this setup.