Last modified: Fri Dec 7 18:06:35 GMT 2007

Administration: Installing Software

Overview

Installing experiment specific software is a Group Administration duty. All software related activities are carried out by a the Experiment Software Manager (ESM) - in our case that's just anyone who is a vo-admin (once our VOMS moves from Manchester to FNAL that will change to minossoft). Normally work is carried by submitting GRID jobs that maintain the software on a dedicated area that is visible to all worker nodes at the site. The top level directory is held in the environmental variable:-

  VO_MINOS_VO_GRIDPP_AC_UK_SW_DIR

A software installation cycle consists of

Allocation of a unique tag for the software build
Installation.
Verification (may be part of Installation).
Add tag to GlueHostApplicationSoftwareRunTimeEnvironment to be published by IS
Removal of redundant builds.

Software tags are managed by the tool lcg-ManageVOTag.

To list, add and remove a tag by hand:-

lcg-ManageVOTag  -host lcgce02.gridpp.rl.ac.uk -vo minos.vo.gridpp.ac.uk --listminos.vo.gridpp.ac.uk

lcg-ManageVOTag  -host lcgce02.gridpp.rl.ac.uk -vo minos.vo.gridpp.ac.uk --add -tag VO-minos.vo.gridpp.ac.uk-Test_Tag_0.0

lcg-ManageVOTag  -host lcgce02.gridpp.rl.ac.uk -vo minos.vo.gridpp.ac.uk --remove -tag VO-minos.vo.gridpp.ac.uk-Test_Tag_0.0

which is used by RSD (Remote Software Deployment), our tool for installing code on the GRID and for MINOS the web-visible directory is:-

  http://www-numi.fnal.gov/computing/remote_software_deployment

Code Specifics

Installing a specific version of the code on the GRID should simply be a case of

Adding a New Build to RSD.

Using RSD to assemble all the required tar files on the RSD web-visible directory. For example:-

  rsd assemble cernlib:2004
  rsd assemble GridTools:`head -1 $MOG_SCRIPTS/maintenance/version_number`  (to assemble the latest version)
  rsd assemble minossoft:R1.26
  rsd assemble minossoft:S07-09-20-R1-26

Using RSD to launch the install of the code on all the required sites and remove obsolete builds. Examples:-


Do these before other installs at a new site:-

rsd launch lcg:lcgce02.gridpp.rl.ac.uk \
     --soft_link=pro:delete --force    \
      GridTools:`head -1 $MOG_SCRIPTS/maintenance/version_number`-build_1

rsd launch lcg:lcgce02.gridpp.rl.ac.uk  \
     --soft_link=pro:delete --force     \
      BFieldMap:2006-01-24-build_1

Then for standard software stacks e.g.:-

rsd launch lcg:lcgce02.gridpp.rl.ac.uk minossoft:R1.23-build_1
rsd launch lcg:lcgce02.gridpp.rl.ac.uk CedarDaikon:03-build_0

To install minossoft:R1.23-build_1 on lcgce02.gridpp.rl.ac.uk. Add option:-

  --install_command_option=--validate_only

to just re-validate an existing install, or:-

  --install_command_option=--force

to force a complete install (normally RSD skips libraries that pass the validation test).

To force re-installation of selected libraries it is sufficient to erase their installation status files and install as follows:-

The location and naming convention of the files is described in RSD Directory Structure:-

$VO_MINOS_VO_GRIDPP_AC_UK_SW_DIR/application_name/application_version/install/scripts/library_name-library_version.status

So, for example for library root:v5-12-00 as part of application minossoft:R1.23-build_1 on lcgce02.gridpp.rl.ac.uk the status file would be:-
```
/stage/sl3-lcg-exp/minossgm/minossoft/R1.23-build_1/install/scripts/root-v5-12-00.status
```

Remove it with:-

  globus-job-run lcgce02.gridpp.rl.ac.uk  /bin/rm /stage/sl3-lcg-exp/minossgm/minossoft/R1.23-build_1/install/scripts/root-v5-12-00.status

Finally re-install :-

rsd launch lcg:lcgce02.gridpp.rl.ac.uk minossoft:R1.23-build_1

rsd launch --remove  lcg:heplnx206.pp.rl.ac.uk minossoft:R1.21-build_1

To remove R1.21-build_1 from heplnx206.pp.rl.ac.uk

Site Specifics

See RSD Site Specifics.

See @ Experiment Software Installation in LCG-2 How The Experiment Software Manager (ESM) installs software.

Return to home page