Install a UI for the csh shell family

The following instructions to install a UI on the user's machine for the csh shell family covers the installation of the EGEE UI and a local condor scheduler. All necessary software can be installed with user privileges and do not require root access. Follow all of the following steps:

Prerequisites

The installation requires ca. 830 MB of free diskspace. To prepare the installation, the user needs to choose a user installation directory and replacing /path/to/ui/location with the full path to this directory. The following commands creates the installation directory:

setenv UI_LOCATION "/path/to/ui/location" 
mkdir -p $UI_LOCATION

EGEE UI installation

The EGEE UI installation follows https://twiki.cern.ch/twiki/bin/view/LCG/TarUIInstall:

  1. Create the EGEE installation directory and change into this directory:
    setenv EGEE_LOCATION $UI_LOCATION/egee
    mkdir -p $EGEE_LOCATION
    cd $EGEE_LOCATION
    
  2. Check that the installation tool yaim is installed on the user's machine with
    rpm -qa | grep -i yaim
    
    If the command returns with no result, yaim has to be installed by:
    wget http://grid-deployment.web.cern.ch/grid-deployment/gis/yaim/glite-yaim-latest.rpm
    rpm2cpio glite-yaim-latest.rpm > glite-yaim-latest.cpio
    cpio -id --verbose --no-absolute-filenames < glite-yaim-latest.cpio
    rm glite-yaim-latest.rpm glite-yaim-latest.cpio
    cd opt
    mv glite ..
    cd $EGEE_LOCATION
    rm -fr opt
    
  3. An ascii file describing your UI installation has to be prepared. Create following file:
    $EGEE_LOCATION/site-info.def
    
    with following content:
    #
    # This is the site-info.def file for my gLite User Interface
    #
    INSTALL_ROOT=$EGEE_LOCATION
    #     
    PX_HOST=myproxy.cern.ch
    WMS_HOST=my-wms.cern.ch
    BDII_HOST=lcg-bdii.cern.ch
    MON_HOST=my-mon.cern.ch
    REG_HOST=my-reg.cern.ch
    VOS="cms"
    #
    USERS_CONF=$INSTALL_ROOT/glite/yaim/examples/users.conf
    JAVA_LOCATION=/usr/java/j2sdk1.4.2_12
    QUEUES="dummy"
    DUMMY_GROUP_ENABLE="dummy" 
    CA_REPOSITORY="rpm http://linuxsoft.cern.ch/ LCG-CAs/current production" 
    #
    VO_CMS_VOMS_SERVERS="'vomss://lcg-voms.cern.ch:8443/voms/cms?/cms/' 'vomss://voms.cern.ch:8443/voms/cms?/cms/'"
    VO_CMS_VOMSES="'cms lcg-voms.cern.ch 15002 /C=CH/O=CERN/OU=computer/CN=host/lcg-voms.cern.ch cms'\
    'cms voms.cern.ch 15002 /C=CH/O=CERN/OU=computer/CN=host/voms.cern.ch cms'"
    #
    
    while replacing $EGEE_LOCATION with the absolute path of that variable and update JAVA_LOCATION according to your system.
  4. Download the latest relocatable middleware and the dependency file from here http://grid-deployment.web.cern.ch/grid-deployment/download/relocatable/. The two tarballs which have to be downloaded are:
    gliteUI_WN-2007-05-15.tar.gz
    gliteUI_WN-userdeps-2007-05-15.tar.gz
    
    where the date *2007-01-15.tar.gz can be different. ExEmplary the download commands for the two tarballs is given here (Version: 05/15/2007):
    wget http://grid-deployment.web.cern.ch/grid-deployment/download/relocatable/gliteUI_WN-2007-05-15.tar.gz
    wget http://grid-deployment.web.cern.ch/grid-deployment/download/relocatable/gliteUI_WN-userdeps-2007-05-15.tar.gz
    
  5. Untar the tarballs:
    tar xzf gliteUI_WN-2007-05-15.tar.gz
    tar xzf gliteUI_WN-userdeps-2007-05-15.tar.gz
    
  6. Install the EGEE UI with:
    $EGEE_LOCATION/glite/yaim/scripts/configure_node $EGEE_LOCATION/site-info.def TAR_UI
    
  7. The previous command installs the CA files and CRLs in the directory $EGEE_LOCATION/glite/etc/grid-security/certificates. It also installs a cron job to keep the CRLs up to date. However it is up to you to install newer versions of the CA files when they are announced. You can install new versions of the CA files executing the following command:
    $EGEE_LOCATION/glite/yaim/scripts/run_function $EGEE_LOCATION/site-info.def install_certs_userland
    
  8. Prepare CMS VO access by creating the following file
    mkdir $EGEE_LOCATION/glite/etc/vomses
    chmod 700 $EGEE_LOCATION/glite/etc/vomses
    touch $EGEE_LOCATION/glite/etc/vomses/cms-lcg-voms.cern.ch
    chmod 600 $EGEE_LOCATION/glite/etc/vomses/cms-lcg-voms.cern.ch
    
    with following content:
    "cms" "lcg-voms.cern.ch" "15002" "/C=CH/O=CERN/OU=computing/CN=host/lcg-voms.cern.ch" "cms"
    
    if it not already exists.

Condor scheduler installation

  1. Create an installation directory for condor and change to it:
    setenv CONDOR_LOCATION $UI_LOCATION/condor
    mkdir -p $CONDOR_LOCATION
    cd $CONDOR_LOCATION
    
  2. Create a directory holding the installation files and change to it:
    mkdir -p $CONDOR_LOCATION/installation
    cd $CONDOR_LOCATION/installation
    
    and download the latest Condor installation tarball from http://www.cs.wisc.edu/condor/downloads/ into this directory. In the following, replace condor.tar,gz with the actual name of this tarball.
  3. Untar the condor installation tarball:
    tar xzf condor.tar.gz
    
    which creates a condor_specific directory in $CONDOR_LOCATION/installation. In the following, replace condor-dir with the actual name of this new directory.
  4. Set following environment variable:
    setenv CONDOR_DOWNLOAD_DIRECTORY $CONDOR_LOCATION/installation/condor-dir
    
  5. Install Condor:
    cd $CONDOR_DOWNLOAD_DIRECTORY 
    condor_configure --install=$CONDOR_DOWNLOAD_DIRECTORY/release.tar --install-dir=$CONDOR_LOCATION --make-personal-condor
    
  6. Adapt the Condor configuration
    $CONDOR_LOCATION/etc/condor_config
    
    by setting following variables replacing $CONDOR_LOCATION and hostname with their actual values:
    RELEASE_DIR = $CONDOR_LOCATION 
    HOSTALLOW_WRITE = "hostname"
    
  7. Prepare the Condor startscript by copying the template startscript
    cp $CONDOR_LOCATION/etc/examples/condor.boot $CONDOR_LOCATION/etc/condor
    
    and changing the MASTER variable of
    $CONDOR_LOCATION/etc/condor
    
    to
    MASTER=$CONDOR_LOCATION/sbin/condor_master
    
    replacing $CONDOR_LOCATION with its actual value.

Start and stop of the Condor scheduler

If used, the Condor scheduler has to run all the time submitted jobs have not finished and has to have a network connection all the time.

To start the Condor scheduler, use

$CONDOR_LOCATION/etc/condor start

To stop it, use:

$CONDOR_LOCATION/etc/condor stop

UI setup script

Prepare the following UI setup script

$UI_LOCATION/ui.csh

with following content:

#!/bin/csh

# gLite UI

setenv UI_LOCATION "/path/to/ui/location"

setenv EGEE_LOCATION $UI_LOCATION/egee

setenv EDG_LOCATION $EGEE_LOCATION/edg
setenv GLITE_LOCATION $EGEE_LOCATION/glite
setenv GLOBUS_LOCATION $EGEE_LOCATION/globus
setenv LCG_LOCATION $EGEE_LOCATION/lcg

source $EGEE_LOCATION/etc/profile.d/grid_env.csh

# condor

setenv CONDOR_LOCATION $UI_LOCATION/condor

setenv CONDOR_CONFIG $CONDOR_LOCATION/etc/condor_config
setenv PATH $PATH:$CONDOR_LOCATION/bin

while replacing /path/to/ui/location with its chosen value.

This script has to be called every time when the user logs into his machine and wants to use the UI.

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2007-06-18 - OliverGutsche
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

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