Installation and configuration of gLite 3.1 on Scientific Linux

General Information

gLite can be installed on a number of RPM capable Linux distributions, but for debugging and support we recommend installing on Scientific Linux 4 or 5.

gLite can also be installed on both 32 and 64bit* Linux architectures.

Please visit the Official gLite Webpage for more information.

WARNING: Until recently the UI had problems to run some glite-wms-job commands on 64bit machines due to python compatibility. It was fixed by adding a 32bit python and changing the python path to this location (under /opt). It is however recommended to install the UI on a 32bit machine, if possible.

OS

• Install Scientific Linux SL4/5.

Choose at least the following installation groups with their default values. A default installation with the following groups will suffice, but you may add additional packages as required.

For 64bit machines, you have to select the following additional groups:

WARNING: Until recently the UI had problems to run some glite-wms-job commands on 64bit machines due to python compatibility. It was fixed by adding a 32bit python and changing the python path to this location (under /opt). It is however recommended to install the UI on a 32bit machine, if possible.

Optionally you may perform the following yum install:

yum -y groupinstall \
"X Window System" \
"Editors" \
"Text-based Internet" \
"Server Configuration Tools" \
"Development Tools" \
"X Software Development" \
"Legacy Software Development" \
"Administration Tools" \
"System Tools" \
"Compatibility Arch Support" \
"Compatibility Arch Development Support"

About New YAIM

In order to configure a site, one or more configuration files are edited and the YAIM script is then executed. Since YAIM is mainly bash, all the configuration files have to follow the bash syntax. For example, no space between the equal sign and the key-value variables are allowed.

YAIM is the service reconfiguration used during the setup procedure. It performs all the needed actions to ensure that all services are configured correctly. YAIM is distributed in several RPMs. The glite-yaim-core contains common functions and definitions, while the other packages like glite-yaim-clients implement the functionality to configure specific node types. The appropriate yaim package will be installed with the service metapackage.

The available yaim modules are:

• glite-yaim-core
• glite-yaim-clients (UI, WN)
• glite-yaim-dpm
• glite-yaim-lcg-ce
• glite-yaim-torque-client
• glite-yaim-torque-server
• glite-yaim-torque-utils
• .................................
• ................................

See the Yaim Modular structure page for more information

The optional folders are created to allow system administrators to organize their configurations in a more structured way. However, it's still possible to use only the site-info.def file and place all the necessary variables for one site there. In case optional folders are used, this is the sourcing flow (where siteinfo refers to the path to the configuration folder):

• siteinfo/site-info.def
• siteinfo/services/*
• siteinfo/nodes/*
• siteinfo/vo.d/*

You can find more details here: YAIM 4 guide

Repository Settings

The default package management tool used by Scientific Linux and YAIM 4 is yum. In order to use the default repositories you may set a temporary variable (on the base of what profile you want to install):

Get the repositories' files with the following command:

For example to get the needed repositories to install a Worker Node with Torque support (ig_WN_torque):

# REPOS="ca dag ig jpackage gilda glite-wn_torque" 

# for name in $REPOS; do wget http://grid018.ct.infn.it/mrepo/repos/$name.repo -O /etc/yum.repos.d/$name.repo; done 

Install Java

Here's an example how to install the required Java packages, but you could decide to follow another solution:

Released Profiles

This is an updated list of the currently deployed profiles with related meta packages and node type names:

OpenAFS

Before installing these meta packages, you should do:

Meta package

To install a Meta package one can perform the following command:

Where <metapackage> is one of the Meta packages from the Released Profiles table (Meta packages column).

-- VanEckA - 18 Aug 2008