Installing an LCG2 Site

From GridPP Wiki
Jump to: navigation, search

There are various components for installation of nodes for use with in GridPP, LCG and EGEE grids. In particular these range from the basic Operating System to middleware such as LCG supplied middleware or very particular components like DCache.

Operating System

Choosing which operating system is really a sites choice but there are certain recomendations that would be obvious. Using operating systems compatable with Redhat Enterprise linux is by far the most commen thing to do. In particular the use of Scientific Linux is highly recommended. The current version in use within LCG is 3.0.X. The minor version X just matches the six month updates that redhat produce with their Redhat Enterprise Range.

Some useful links in these areas are:

In particular any tips or suggestions concerning installation with kickstart, such as how to mirror SL or will be placed there.


Installing LCG2

There are really two suggested methods that can be used, generic YAIM installation and the complete Quattor installation.

The main difference here is that YAIM is only a method for installation and configuration of LCG middleware. It is not a complete solution for installing nodes. YAIM must therefore be used in conjuction with some other installation such as writing kickstart files by hand. YAIMs interface is simple enough that it can problably be inserted into any installation method that you are using such as cfengine, xcat,...

Quattor is complete solution which will handle installation of nodes from bare metal, operating system and then LCG middleware.

Links in this area include:

The quattor homepage describes with tutorials and manuals how to install and use quattor in a generic way for installing and maintaining nodes. The EGEE quattor working group is coordinating the effort to use Quattor for the installation of grid nodes within EGEE and LCG.

Storage Resource Management

Please read the Tier-2 storage support document before you start deploying an SRM.

About this page

This page is maintained by Steve Traylen.