AFS UI Manuall Installation

Install the software

• Download the tarball directly from the repositories or from the UI update page
  • repositories
    • 3.0: old relocateable repository
    • 3.1: SLC4_x86 repository

• • UI updates page: http://glite.web.cern.ch/glite/packages/R3.0/deployment/glite-UI/glite-UI.asp
• Go to the AFS UI writable root directory (note the extra dot)

    cd /afs/.cern.ch/project/gd/LCG-share

• Make a new directory named after the version to be installed, which we call here $VERSION_STRING.

    mkdir ${VERSION_STRING}

• Go to that directory

    cd /afs/.cern.ch/project/gd/LCG-share/${VERSION_STRING}

• Untar the tarballs e.g. like this:

    tar xzf gliteUI_WN-2006-12-18.tar.gz
    tar xzf gliteUI_WN-userdeps-2006-12-18.tar.gz

Reconfigure (with yaim)

Note: this currently requires some post-installation steps at CERN, as each VO normally has more than one RB, and different per VO, which currently is not supported by YAIM.

Pre-configuration steps

• Customize the configuration file
  • In the root directory, edit the site-info.def
    • set the INSTALL_ROOT to /afs/.cern.ch/project/gd/LCG-share/${VERSION_STRING}
    • make sure there is no reference to /opt anywhere (should be $INSTALL_ROOT everywhere)
    • Make sure you set

                             CRONJOB_DIR=/dev/null

• In your shell set these environment variables:

    setenv INSTALL_ROOT /afs/.cern.ch/project/gd/LCG-share/${VERSION_STRING}
    setenv X509_CERT_DIR /afs/cern.ch/project/gd/LCG-share2/certificates

• Unset JAVA_HOME

    unsetenv JAVA_HOME

• Move the $HOME/.glite directory out of the way, otherwise it will pollute the new environment scripts with obsolete values

    mv $HOME/.glite $HOME/.glite_save

Link to bug or ticket if present	Hack to fix it
savannah 23821	Rename the directory $HOME/.glite to a different name
savannah 23822	Unset JAVA_HOME

Run yaim

    cd $INSTALL_ROOT
    ./glite/yaim/scripts/configure_node site-info.def TAR_UI  | tee update_`date +%y%m%d%H%M`.log

Post install steps

• Change the ownership of the vomses file and the vomsdir directory entries:

     afs_admin s_o root:root $INSTALL_ROOT/edg/etc/vomses 
     afs_admin s_o root:root $INSTALL_ROOT/edg/etc/vomses/* 
     afs_admin s_o root:root $INSTALL_ROOT/glite/etc/vomses 
     afs_admin s_o root:root $INSTALL_ROOT/external/etc/grid-security/vomsdir
     afs_admin s_o root:root $INSTALL_ROOT/external/etc/grid-security/vomsdir/* 

• Change the environment scripts grid.sh, grid.csh and glite_setenv.sh, glite_setenv.csh under $INSTALL_ROOT/etc/profile.d to use the read-only volume: change instances of /afs/.cern.ch to /afs/cern.ch in the paths.

Known Bugs

The next step is to bugfixing. For the list of known bugs, and hacks how to fix them, please refer to the List of known bugs.

Check the differences with the current AFS UI release

• Run a recursive diff like this:

     diff -r 3.x.y-z ${VERSION_STRING} > diffs.txt

• Check the sanity of the diffs for each configuration file (e.g. in "less diffs.txt" search for lines starting with "diff")

• Check for files that only appear in one of the releases:

  grep ^Only diffs.txt | less
     

  Obsolete files may disappear, new files may appear, but are there unexpected changes?

Test the new release

• Check that the VO configuration is correct. Hints are given VO-related operations on AFS UI
• Start a new session on lxplus (do not use an existing session)

• Source the new grid_env.sh or grid_env.csh

• Run various test commands:

    edg-job-submit ...
    glite-job-submit ...
    lcg-cr ...
    ...

If all looks well

• Point the sl3 symlink to the new release (if already desired)

• Synchronise as described Syncronize read-only copy on AFS

• Make a backup of the new release

    cd /afs/.cern.ch/project/gd/LCG-share
    gtar cfz /afs/cern.ch/project/gd/afs-ui-bkp/AFS-UI-$VERSION_STRING-`date +%y%m%d`.tgz \
        $VERSION_STRING

• Remove old backups that should no longer be needed (be careful).

-- JuditNovak - 04 Oct 2007 -- FaridaNaz - 12 Nov 2007