# GlideinWMS The Glidein-based Workflow Management System

- Home
- Download
- Glidein Frontend
- Corral Frontend
- WMS Factory
- Components
- FAQ

Loading

## Search Results

## GlideinWMS

- Overview
- Download
- Documentation
- Install
- History
- License

### Installation

Jump to:

1. Installation Process
2. Using the OSG Factory
3. Configuration-based Installer
4. Installation Process
5. Additional documents
6. Possible Configurations
7. Connecting to OSG Factory

Installation at a glance:

1. Pre-requisites
2. WMS Collector and Factory
3. User Pool Collector
4. User Pool Schedd
5. Glidein Frontend

Configuration based installer
Upgrade Guide

### Installation Process

Installation of glideinWMS is a multi-step process:

1. Components and Pre-requisites and set up GSI certificates.
2. The glidein WMS Collector and collocated glidein Factory node
3. The glidein pool Collector node
4. One or more scheduler nodes for user submission
5. The Glidein Frontend
6. Submitting a job

The above process should suffice for typical installs. For OSG sites connecting to the UCSD OSG factory, see the following section. More information can be found below.

### Using the OSG Factory

Members of the Open Science Grid can use the OSG factory at UCSD. In this case, you should install only a partial sub-set of services (the factory will be provided for you. Follow these steps (in order):

1. glidein pool Collector
2. scheduler for user submissions
3. Glidein Frontend

You will also need access to (at least) two proxies for the frontend and glideinsi, which will need to be sent to the factory operators. See OSG Glidein Factory for more details on how to use this setup.

### Configuration based installer

Alternatively, you can use the Configuration based installer. This approach requires filling out a configuration file (ini file) with all the required fields up front. Once this is done, you can install each component using the tool and this ini file. It prevents the frustration of running the Q&A installer multiple times in case of errors.

Important Note: You can only use either the Q&A installer to install all components or the configuration based installer to install all components. You cannot mix installations by installing partially with the Q&A installer and partially with the configuration installer. Also, note that both installers assume you are performing a full installation of all components. For upgrades, see the upgrade guide or contact glidein support.

### 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.