# GlideinWMS The Glidein-based Workflow Management System

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

Loading

## Search Results

## Components

- Overview
- Prerequisites
- User Collector
- User Schedd
- GSI
- Condor

### Prerequisite Component Installation

Jump to:

1. HTTPD Server
2. OSG VDT Client
3. RRDTool
4. M2Crypto
5. javascriptRRD

Installation Procedure
Preceded by: Installation Overview
Followed by: Factory Install
Install as: various daemon users or as system rpms/packages
Configuration based installer

## Installation of the WMS Components with the Installer

Before you begin make sure the following software is either installed or available for installation.

Software | Version | WMS collector | Factory | User collector | Submit | Glidein Frontend | Comments
glideinWMS | v2.4 | y | y | y | y | y |
Condor | v7.2.+ | y |  | y | y | y | SL3 x86 binaries should work everywhere. For x86_64 OSG, you need to install 32 bit compatibility libraries. It is HIGHLY recommended that the SL3 x86 binaries be used.
OSG client | current version | y |  | y | y | y | Needed to generate grid/voms proxies.
Python | v2.3.4+ | y | y | y | y | y |
HTTP server | latest version |  | y |  |  | y | Apache, TUX or server of choice.
RRDTool | V1.1.18+ |  | y |  |  | y | http://dag.wieers.com/rpm/packages/rrdtool/rrdtool-1.2.18-1.el4.rf.i386.rpm http://dag.wieers.com/rpm/packages/rrdtool/perl-rrdtool-1.2.18-1.el4.rf.i386.rpm http://dag.wieers.com/rpm/packages/rrdtool/python-rrdtool-1.2.18-1.el4.rf.i386.rpm
M2Crypto | v0.17+ |  | y |  |  | y | This can be installed using yum, if available. Or via a tarball from http://chandlerproject.org/Projects/MeTooCrypto#Downloads
javascriptRRD with Flot | v0.6.0 |  | y |  |  | y | http://sourceforge.net/projects/javascriptrrd/files/javascriptrrd/ Note: JavascriptRRD and flot, are available from different sources however they may not always work when installed for glideinWMS. We only support JavascriptRRD with Flot available from the sourceforge link above

## 1. HTTP server

To use the installer, move into

> glideinWMS/install

and execute (as root)

> ./glideinWMS_install

You will be presented with this screen:

> What do you want to install?
> (May select several options at one, using a , separated list)
> [1] glideinWMS Collector
> [2] Glidein Factory
> [3] GCB
> [4] pool Collector
> [5] Schedd node
> [6] Condor for Glidein Frontend
> [7] Glidein Frontend
> [8] Components

Select 8.

You will be given another menu:

> What do you want to install?
> (May select several options at one, using a , separated list)
> [a] OSG VDT client
> [b] Base Condor installation
> [c] Web server
> [d] rrdtool graphics package
> [e] PostgreSQL database
> [f] Quill-specific PostgreSQL database

Select c.

Now follow the instructions. Most of the questions should be fairly straightforward.

Make sure that you install this service on a port that can be accessed by the internet, as worker nodes will need to be able to communicate with this port to download data.

## 2. OSG VDT Client

At times the installer will give you the option to install the OSG VDT client. Below is an example of an intall for reference. It can also be installed using the installer.
Notes:

- Unless you know of a need to use a different version, accept the default pacman version listed by the installer
- Allow the installer to auto-detect your platform unless you want to force a specific platform
- Use the default OSG location, unless you have good reason to change it
- Unless you want your users to have to find and define the OSG VDT Client location themselves, when asked, answer 'y' to defining OSG_VDT_BASE globally

    Do you want to install the full OSG VDT client?: (y/n) y
    Where do you want the VDT installed?: [/opt/vdt] /opt/vdt
    Directory '/opt/vdt' does not exist, should I create it?: (y/n) y
    What pacman version should I use?: [3.28] 3.28

    --2010-05-06 13:34:52--  http://vdt.cs.wisc.edu/software/pacman/3.28/pacman-3.28.tar.gz
    Resolving vdt.cs.wisc.edu... 128.105.121.78
    Connecting to vdt.cs.wisc.edu|128.105.121.78|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 856103 (836K) [application/x-gzip]
    Saving to: `pacman-3.28.tar.gz'

    100%[=====================================================================================================================================================================>] 856,103     --.-K/s   in 0.09s

    2010-05-06 13:34:52 (9.03 MB/s) - `pacman-3.28.tar.gz' saved [856103/856103]

    pacman-3.28/

The contents of the tarball have been removed for space reasons.

    pacman-3.28/bin/pacman

    VDT client installation tends to be very picky about the platforms it installs under
    Most of the time, one needs to pretent to be one of the tested platforms
    The platforms known to work are: linux-rhel-4,SL-4,linux-rhel-5,SL-5
    Which platform do you want to use (leave empty for autodetect):

    The VDT installation will start in a moment.
    CA certificates are installed as part of this procedure; ignore the VDT warning message.
    Please do not enable Condor, as we will install it separatelly.

    Beginning VDT prerequisite checking script vdt-common/vdt-prereq-check...

    All prerequisite checks are satisfied.

    ========== IMPORTANT ==========
    Most of the software installed by the VDT *will not work* until you install
    certificates.  To complete your CA certificate installation, see the notes
    in the post-install/README file.

    The VDT version 2.0.0 has been installed.

    The OSG Client package OSG version 1.2.9 has been installed.
    VDT does not provide a default URL for CA fetching
    You need to provide one
    The default OSG location is: http://software.grid.iu.edu/pacman/cadist/ca-certs-version
    Where should I fetch the CAs from?: [http://software.grid.iu.edu/pacman/cadist/ca-certs-version]http://software.grid.iu.edu/pacman/cadist/ca-certs-version
    Setting CA Certificates for VDT installation at '/opt/vdt'

    Setup completed successfully.
    running 'vdt-register-service --name vdt-update-certs --enable'... ok
    running 'vdt-register-service --name fetch-crl --enable'... ok
    running 'vdt-register-service --name vdt-rotate-logs --enable'... ok
    enabling cron service fetch-crl... ok
    enabling cron service vdt-rotate-logs... ok
    enabling cron service vdt-update-certs... ok
    skipping init service 'condor' -- marked as disabled
    skipping init service 'globus-ws' -- marked as disabled
    Do you want OSG_VDT_BASE defined globally?: (y/n) y

    VDT client installed

### 3. RRDTool

You will also need the python module for RRDTool (v1.2.18 or later). Many systems come with packages for it; if possible use that.

RPMs for Redhat/Scientific Linux distributions can be found at http://dag.wieers.com/rpm/packages/rrdtool/

Install python-rrdtool*.rpm and related dependencies.

If installing as root is not an option, you can build from the sources, as the glidein factory user, and put the python libraries into the PYTHON_PATH.
The source code can be downloaded from: http://oss.oetiker.ch/rrdtool/pub/

Beware: The build process has several dependencies that make it complicated. Use this option only if you cannot install from RPMs (or similar).

### 4. M2Crypto

You will need the M2Crypto python library. A few systems include it in the software distribution; if possible install the system one.

If your system does not come with m2crypto package, or you do not can/want install it as root, compile it from source as the glidein factory user.
The source code can be downloaded from: http://chandlerproject.org/Projects/MeTooCrypto#Downloads

The build process is very easy:

> python setup.py build
> python setup.py install --root <base dir>

Finally add M2Crypto site-packages into the PYTHONPATH, possibly in the .profile, .bashrc and/or in the .cshrc.
The exact path is system specific. On a 32bit system with python 2.3.x it will look like this:

> export PYTHONPATH=$PYTHONPATH:<base dir>/usr/lib/python2.3/site-packages/

### 5. javascriptRRD

You will need the javascriptRRD package. It contains the javascript libraries needed by the monitoring. Just download the tarball (with flot), and untar it. You will need to point the installer to this directory.