AFS UI Manuall Installation

Install the software

• Download the tarball from the UI update 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.

Hacks to fix known bugs

gLite 3.0

Link to bug or ticket if present	Hack to fix it
GGUS 17491 savannah 23285	Both environment scripts need to be sourced. Add the following line to grid_env.sh source ${INSTALL_ROOT}/etc/profile.d/glite_setenv.sh and the following to grid_env.csh source $INSTALL_ROOT/etc/profile.d/glite_setenv.csh
savannah 18024	Copy an old vomses file into the glite/etc/ directory.
savannah 22510	Ensure that the following file for the WMS, $INSTALL_ROOT/glite/etc/glite_wmsui_cmd_var.conf plus one file per vo: $INSTALL_ROOT/glite/etc/$VO/glite_wms.conf have these lines: ErrorStorage = "/tmp"; OutputStorage = "/tmp"; ListenerStorage = "/tmp"; # LoggingDestination = "some-node.cern.ch:9002"; # it must be commented out or absent DefaultVo = "unspecified"; Usually the storage variables refer to /tmp/glite/glite-ui, and the default VO to dteam..
savannah 22942 savannah 23746	Configure the VOs as described here. We suggest you copy the files from the previous version of the UI, changing them if necessary.
savannah 23756	Two entries for the PYTHONPATH variables should be removed from the environment profile.d files glite_setenv.(c)sh: $INSTALL_ROOT/glite/lib/python2.2 $INSTALL_ROOT//glite/lib/python2.2/site-packages
savannah 24713	Copy the content of the .edg/vomses directory into the ${INSTALL_ROOT}/edg/etc/vomses directory.
savannah 24714	Ensure that the two files for the RB $INSTALL_ROOT/edg/etc/edg_wl_ui_cmd_var.conf and $INSTALL_ROOT/edg/etc/edg_wl_ui_gui_var.conf, have these lines: # LoggingDestination = "some-node.cern.ch:9002"; # it must be commented out or absent DefaultVo = "unspecified"; If this line is present and more than one RB is used it will cause errors as the LoggingDestination depends form the RB and is picked up automatically by the system if not set.
savannah 24820	Move the DPM RFIO client commands (if any) out of the way, because they cannot (yet) work with CASTOR: cd ${INSTALL_ROOT}/lcg/bin mkdir dpm mv rf* dpm
savannah 25866	Globus development environment is not configured. You should set two environment variables and run the gpt-build command: export GLOBUS_LOCATION=/afs/.cern.ch/project/gd/LCG-share/X.Y.Z-W/globus/ export GPT_LOCATION= /afs/.cern.ch/project/gd/LCG-share/X.Y.Z-W/gpt/ ${GPT_LOCATION}/sbin/gpt-build -force -nosrc gcc32 gcc32pthr gcc32dbg gcc32dbgpthr

gLite 3.1

Link to bug or ticket if present	Hack to fix it
savannah 28491	Copy a working tcsh envoronment script from the previous release and modify it accordingly (new dir for new installation and compare it with its bash equivalent.
savannah 18024	Copy an old vomses file into the glite/etc/ directory.
savannah 24713	Copy the content of the .edg/vomses directory into the ${INSTALL_ROOT}/edg/etc/vomses directory.
savannah 22942 savannah 23746	Configure the VOs as described here. We suggest you copy the files from the previous version of the UI, changing them if necessary.
savannah 24820	Move the DPM RFIO client commands (if any) out of the way, because they cannot (yet) work with CASTOR: cd ${INSTALL_ROOT}/lcg/bin mkdir dpm mv rf* dpm
savannah 22510	Ensure that the following file for the WMS, $INSTALL_ROOT/glite/etc/glite_wmsui_cmd_var.conf plus one file per vo: $INSTALL_ROOT/glite/etc/$VO/glite_wms.conf have these lines: ErrorStorage = "/tmp"; OutputStorage = "/tmp"; ListenerStorage = "/tmp"; # LoggingDestination = "some-node.cern.ch:9002"; # it must be commented out or absent DefaultVo = "unspecified"; Usually the storage variables refer to /tmp/glite/glite-ui, and the default VO to dteam..
savannah 24714	Ensure that the two files for the RB $INSTALL_ROOT/edg/etc/edg_wl_ui_cmd_var.conf and $INSTALL_ROOT/edg/etc/edg_wl_ui_gui_var.conf, have these lines: # LoggingDestination = "some-node.cern.ch:9002"; # it must be commented out or absent DefaultVo = "unspecified"; If this line is present and more than one RB is used it will cause errors as the LoggingDestination depends form the RB and is picked up automatically by the system if not set.
GGUS 17491 savannah 23285	Both environment scripts need to be sourced. Add the following line to grid_env.sh source ${INSTALL_ROOT}/etc/profile.d/glite_setenv.sh and the following to grid_env.csh source $INSTALL_ROOT/etc/profile.d/glite_setenv.csh
savannah 25866	Globus development environment is not configured. You should set two environment variables and run the gpt-build command: export GLOBUS_LOCATION=/afs/.cern.ch/project/gd/LCG-share/X.Y.Z-W/globus/ export GPT_LOCATION= /afs/.cern.ch/project/gd/LCG-share/X.Y.Z-W/gpt/ ${GPT_LOCATION}/sbin/gpt-build -force -nosrc gcc32 gcc32pthr gcc32dbg gcc32dbgpthr
savannah 23756	Two entries for the PYTHONPATH variables should be removed from the environment profile.d files glite_setenv.(c)sh: $INSTALL_ROOT/glite/lib/python2.2 $INSTALL_ROOT//glite/lib/python2.2/site-packages
savannah 27362	$INSTALL_ROOT/etc/profile.d links are incorrect. The links should be set up as the following grid-env.csh -> ../../external/etc/profile.d/grid-env.csh grid-env.sh -> ../../external/etc/profile.d/grid-env.sh grid_env.csh -> ../../external/etc/profile.d/lcgenv.csh grid_env.sh -> ../../external/etc/profile.d/lcgenv.sh lcgenv.csh -> ../../external/etc/profile.d/lcgenv.csh lcgenv.sh -> ../../external/etc/profile.d/lcgenv.sh

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