TWiki> LCG Web>LCGGridDeployment>LcgDocs>TarUIInstall (revision 31)EditAttachPDF

How to install the TAR_UI


This page describes how to install a UI as a non root-user. For this purpose we provide a tarball distribution that can be untarred into any directory. In addition we provide a tarball containing gLite dependencies which might be missing on your host machine. The tarball also contains the contains all the files needed for WN, thus it can be also used to install a WN into any directory. For more detailed documentation have a look a the "The relocatable distribution" section in the Generic Installation and Configuration Guide. For glite 3.1 SLC4 look at WnTarInstall.

Supported OS

The tarball is fully supported on SL(C)3 on x86. It should also work on SL(C)4 on x86 and x86_64 in compatability mode (lxplus setup at CERN). Have a look at the Known issues section.


The relocatable ditribution is divided into two tarballs. One containing the gLite UI and WN files and another one containing dependencies. The tarball is versioned by its date of creation. As an example you find something like
for the UI/WN files resp. the dependencies. In addition we provide tarballs for the pre production service (PPS). These tarballs contain the string "PPS", e.g.
Download the latest relocatable middleware and the dependency file from here Have a look at the README which contains information about UI and WN versions. The tarball contains a file ${INSTALL_ROOT}/glite/etc/relocatable-release with information about the rpms contained therein.

Create a directory for the middleware, e.g. ~/gLite :

      mkdir gLite
Install the tarball in this directory
       cd ~/gLite
       tar -zxvf gliteUI_WN-2007-01-22.tar.gz
       tar -xzvf gliteUI_WN-userdeps-2007-01-22.tar.gz


Create a site-info.def file gLite/site-info.def with the following necessary variables, adapted to your needs: (Some of them are not used but have to be set to some dummy value.)

      INSTALL_ROOT=<the directory where you untar, e.g. $HOME/gLite>
      PX_HOST=<myproxy server hostname>
      WMS_HOST=<wms hostname>
      BDII_HOST=<top level bdii hostname>
      MON_HOST=<mon box hostname>
      REG_HOST=<RGMA registry hostname>
      VOS="<list of supported VOS, e.g. dteam>"

      JAVA_LOCATION=<location of your Java installation, e.g. /usr/java/j2sdk1.4.2_12>
      CA_REPOSITORY="rpm LCG-CAs/current production" 

     # The follwing two variables have to be defined for every VO listed in VOS
      VO_<VO-NAME>_VOMS_SERVERS=<list of VOMS servers for the VO VO-NAME>
      VO_<VO-NAME>_VOMSES=<List of entries for the vomses files for VO VO-NAME>
If you would like to use other VOs have a look to the example file (./glite/yaim/examples/site-info.def) or visit the page to get some information about other VOs. For other variables relevant to the UI yaim will assume default values if they are not present in the site-info.def file. A list of all variables can be found in the Yaim 3.0.1 Guide. In particular you might want to define the following variables:
ATTENTION: Please make sure that the already defined enviroment variables and the site-info.def variables do not conflict ! The best is to perform the configuration in a 'clean' enviroment.

Installation for PPS tarball as of 2007-03-26 release and production tarball as of 2007-04-16 release

Make sure that at least the variables listed in the above sample site-info.def file are present and have the values needed for your site. As of this release yaim 3.0.1 is contained in the tarball. Have a look at the user guide. For configuring the TAR_UI use the following command:

       cd ~/gLite
      ./glite/yaim/bin/yaim -c -s ./site-info.def -n TAR_UI

Installation for older tarballs

Make sure that the file ./glite/yaim/functions/install_certs_userland contains the right URL for downloading the certificates:

Now configure the TAR_UI:
       cd ~/gLite
       ./glite/yaim/scripts/configure_node ./site-info.def TAR_UI

General remarks for the installation

The installation scripts puts glite_setenv.(c)sh into ~/.glite/ and adds a line to .bashrc or .tcshrc. So this environment is set up every time you log in. You find this file also in ${INSTALL_ROOT}/etc/profile.d/. In addition you have to source the file ${INSTALL_ROOT}/etc/profile.d/grid_env.(c)sh (this is not being done automatically).

If you reinstall a TAR_UI you should remove an already existing ~/.glite/glite_setenv.(c)sh beforehand.

Installing a UI this way puts all the CA certificates under $INSTALL_ROOT/etc/grid-security and adds a user cron job to download the crls. However, please note that you'll need to keep the CA certificates up to date yourself. You can do this by running

       $INSTALL_ROOT/glite/yaim/scripts/run_function site-info.def install_certs_userland
Make sure you have your certificate and private key in your .globus directory. Now do a
      voms-proxy-init -voms yourVO
to get started.

Known issues

Test coverage of the TAR_UI

To test the TAR_UI (and also the rpm based UI) we have developed an extensive set of tests. However for the API's we currently don't have a comprehensive test suite.

TAR_UI on SL(C)4

The tarballs contain rpms targeted for SL(C)3 on x86. However it has been verified that the binaries can be also run on SL(C)4 on x86 and x86_64 in compatability mode (lxplus setup at CERN). The userdeps tarball contains a complete Python distribution as found on SL(C)3 but not a Perl distribution. Sourcing the two files mentionend in the Configuration section the user's PATH is modified such that bin dirs in the userdeps tarball are searched for first. With this setup the UI tests pass but you might see problems when using the APIs.

Missing dependencies

The userdeps tarball contains non-gLite files the UI depends on but which cannot be expected on a standard SL(C)3 installation. The userdeps tarball is created on a best effort bases but there is currently no document describing what has to be installed on the SL* machine hosting the TAR_UI. You might find out that your SL* installation is missing some rpms.

UI installation on lxplus

Have a look at AFS UI TWiki.

Open bugs

#20781, #20790, #20791, #23004, #23285, #23548, #23668, #23718, #24224, 28566, 28567. See also the bugs listed on AFS UI.

Support for Debian

Debian is not officially supported. Here is a list of packages which are required for the tarball to work
      perl-modules python2.2 libexpat1 libx11-6 libglib2.0-0 libldap2 libstdc++2.10-glibc2.2 tcl8.3-dev 
      libxml2 termcap-compat libssl0.9.7 tcsh rpm (librpm4) rsync cpp gawk openssl wget python-xml


Andreas Unterkircher

-- AndreasUnterkircher - 25 Apr 2007

Edit | Attach | Watch | Print version | History: r33 < r32 < r31 < r30 < r29 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r31 - 2007-08-06 - JoachimFlammer
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback