From ATLAS-TRIUMF

Instructions here are for a 32-bit OS; please check the yum repositories before you download 64 bit versions.

[edit] Install Scientific Linux

Install Scientific Linux on your computer; you can choose any packages or versions you like but make sure that the following are also installed:

• OpenAFS
• Development Tools
  • also select gfortran

I did not enable the firewall for my installation because there was a warning about OpenAFS not working with it; I do not know if this is still true. (Needs testing).

[edit] Setup Kerberos

Kerberos is the preferred method to access the cvs repository at CERN. To set this up, add the following to these files:

• /etc/krb5.conf

CERN.CH = {
  default_domain = cern.ch
  kpasswd_server = afskrb5m.cern.ch   
  admin_server = afskrb5m.cern.ch
  kdc = afsdb1.cern.ch
  kdc = afsdb2.cern.ch
  kdc = afsdb3.cern.ch
  v4_name_convert = {
     host = {
         rcmd = host
     }
  }
 }
.cern.ch = CERN.CH

• /etc/krb.conf

CERN.CH

CERN.CH afsdb1.cern.ch
CERN.CH afsdb3.cern.ch
CERN.CH afsdb2.cern.c

• /etc/krb.realms

.cern.ch CERN.CH
.wgs.cern.ch CERN.CH
.plus.cern.ch CERN.CH

To test that this works, do the following:

kinit -4 -5 user@CERN.CH
(replace <user> with your username)

Note that the uppercase address CERN.CH is important.

You should see the tickets with

klist

and destroy the active tickets with

kdestroy

It looks like sourcing some of the CMT setup scripts changes the path to kinit and you may be pickup up a wrong version. if you get an error with kinit, log in a fresh session and do

which kinit

Note the path and always source that version of kinit. In any case, you should do a kinit after you login and before sourcing any other scripts.

[edit] Install gLite-UI

gLite is the grid middle-ware, which are tools to enable you to run your jobs on the Grid. In principle, you can just source the setup script from CERN via afs and submit the jobs on the grid. However, this seems slow ...

[edit] For single user without root access

Fetch the tar files from the LCG site - I've installed the two files below:

• do

 mkdir ~/gLite; cd ~/gLite
 gtar zxf glite-UI-3.1.0-1-external.tar.gz 
 gtar zxf glite-UI-3.1.0-1.tar.gz 

• create a file ~/gLite/site-info.def

INSTALL_ROOT=$HOME/gLite
JAVA_LOCATION=/usr/java/j2sdk1.4.2_12
MY_DOMAIN=triumf.ca

GLITE_EXTERNAL_ROOT=${INSTALL_ROOT}/external
GRID_ENV_LOCATION=${GLITE_EXTERNAL_ROOT}/etc/profile.d

PX_HOST=myproxy.cern.ch
WMS_HOST=rb106.cern.ch
RB_HOST=rb106.cern.ch
BDII_HOST=lcg-bdii.cern.ch
MON_HOST=lcggiis01.$MY_DOMAIN
REG_HOST=lcgic01.gridpp.rl.ac.uk
CA_REPOSITORY="rpm http://linuxsoft.cern.ch/ LCG-CAs/current production"
FUNCTIONS_DIR=$INSTALL_ROOT/glite/yaim/functions

VOS="atlas"
VO_ATLAS_VOMS_SERVERS="'vomss://lcg-voms.cern.ch:8443/voms/atlas?/atlas/' 'vomss://voms.cern.ch:8443/voms/atlas?/atlas/'"
VO_ATLAS_VOMSES="'atlas lcg-voms.cern.ch 15001 /C=CH/O=CERN/OU=GRID/CN=host/lcg-voms.cern.ch atlas' 'atlas voms.cern.ch 15001 /C=CH/O=CERN/OU=GRID/CN=host/voms.cern.ch atlas'"
USERS_CONF=./glite/yaim/examples/users.conf

• Run the installation configuration:

 ./glite/yaim/bin/yaim -c -s site-info.def  -n UI_TAR

When you log in to a fresh session, do

 source ~/gLite/etc/profile.d/grid_env.sh; source ~/gLite/etc/profile.d/lcgenv.sh

To run a job, you need to do voms-proxy-init and not grid-proxy-init.

[edit] Yum install method - For all users on computer

To install this user interface, you first need to set up the repository: (Instructions found on this LCG Wiki.)

• create a file /etc/gLite.repo

[glite-WN]
name=gLite 3.1 Worker Node
baseurl=http://linuxsoft.cern.ch/EGEE/gLite/R3.1/glite-WN/sl4/i386/
enabled=0

[glite-TORQUE_client]
name=Torque clients
baseurl=http://linuxsoft.cern.ch/EGEE/gLite/R3.1/glite-TORQUE_client/sl4/i386/
enabled=0

[glite-UI]
name=gLite 3.1 User Interface
baseurl=http://linuxsoft.cern.ch/EGEE/gLite/R3.1/glite-UI/sl4/i386/
enabled=1

• create a file /etc/jpackage.repo

[main]
[jpackage17-generic]
name=JPackage 1.7, generic
baseurl=http://mirrors.dotsrc.org/jpackage/1.7/generic/free/
enabled=1
protect=1

[main]
[jpackage5-generic]
name=JPackage 5, generic
baseurl=http://mirrors.dotsrc.org/jpackage/5.0/generic/free/
enabled=1
protect=1

• create a file /etc/cas.repo

[CA]
name=CAs
baseurl=http://linuxsoft.cern.ch/LCG-CAs/current

• make sure /etc/dag.repo has enabled=1

Then do a

yum install glite-UI

followed by a

 yum install lcg-CA

Note that for the UI, I did not need to install a new java version; the version installed by SL4 (1.4.2_12 seems to work.)

The gLite package will be installed in /opt.

Create a file /opt/glite/site-info.def:

INSTALL_ROOT=/opt
PX_HOST=myproxy.cern.ch
WMS_HOST=rb106.cern.ch
RB_HOST=rb106.cern.ch
BDII_HOST=lcg-bdii.cern.ch
MON_HOST=mon.cern.ch
REG_HOST=lcgic01.gridpp.rl.ac.uk
VOS="atlas"
VO_ATLAS_VOMS_SERVERS="'vomss://lcg-voms.cern.ch:8443/voms/atlas?/atlas/' 'vomss://voms.cern.ch:8443/voms/atlas?/atlas/'"
VO_ATLAS_VOMSES="'atlas lcg-voms.cern.ch 15001 /C=CH/O=CERN/OU=GRID/CN=host/lcg-voms.cern.ch atlas' 'atlas voms.cern.ch 15001 /C=CH/O=CERN/OU=GRID/CN=host/voms.cern.ch atlas'"
USERS_CONF=./glite/yaim/examples/users.conf

Next, as a super user, do the following:

 cd /opt
 /opt/glite/yaim/bin/yaim -c -s glite/site-info.def -n UI

The VOMs will be also installed for ATLAS in /opt/edg/etc/vomses (and maybe also in /opt/glite/etc/vomses).

The setup files will be installed in /etc/profile.d:

grid-env.csh -> /opt/glite/etc/profile.d/grid-env.csh
grid-env.sh -> /opt/glite/etc/profile.d/grid-env.sh
lcgenv.csh
lcgenv.sh

which will be automatically sourced for every user's login.

To test that this works, make sure that the user has a ~/.globus directory with the key and pass certificates. Then run a hello world job as outlined in the workbook. (Note, you need to do voms-proxy-init, not grid-proxy-init.)

[edit] Upgrading Software

(Note that with SL4, yum updates the packages automatically in a nightly job. To turn this off / on, go to the

Application -> System Settings -> Server Settings -> Services 

panel and click on the box for yum; you may also have to stop/start the server if it is running/stopped. A log file of installed/updated packages will be in /var/log/yum.log. These instructions were for GNOME desktop; there is a similar setup for KDE.) On a personal note, I prefer to do this manually so that I am aware of what changes there are in my computer rather than be surprised !

With yum, it is easy to upgrade the installed software to the latest versions. Yum will check that there are no conflicts with dependencies before installation or any upgrades. Yum relies on depositories which are configured in /etc/yum.repos.d - you need to have system privileges to use yum.

To upgrade, simply do

yum update

To see what is installed, do a

 yum list

(Alternately, you can also do a rpm -qa to list all the installed rpm packages on your computer; you do not need system privileges for this.)

To see install only a particular package, do

 yum install <package>

Important :

• If you do a kernel upgrade, you also need to reboot and follow up by doing an upgrade to the OpenAfs kernel module:

yum list kernel-module-openafs-`uname -r`

• Do not do automatic updates - gLite (Grid middleware) recommends against doing this. You can update everything else by exclude this repository with a yum flag:

yum update --disablerepo=glite* --disablerepo=jpackage* --disablerepo=dag

(or set disable them in /etc/yum.repos.d)