EMI UI TAR

Introduction

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, all the executables and libraries needed from the UI are inside the tarball.

Supported OS

The tarball is fully supported on SL(C)5 on x86_64. Have a look at the Known issues section.

Installation

The relocatable distribution is in one tarball: the EMI UI Tarball - the file contains the main distribution and the dependencies. You can download the latest relocatable middleware and the dependency file from:

Have a look at the README which contains information about UI and WN versions. The tarball contains a file ${INSTALL_ROOT}/content.txt with information about the rpms contained therein.

Create a directory for the middleware, e.g. ~/emi-ui :

      cd
      mkdir emi-ui
Install the tarball in this directory
       cd ~/emi-ui
       wget http://emisoft.web.cern.ch/emisoft/dist/EMI/testing/1/sl5/x86_64/tgz/emi-ui-1.0.0-3.sl5-x86_64.tar.gz
       tar -zxvf emi-ui-1.0.0-3.sl5-x86_64.tar.gz

Configuration

Create a site-info.def file emi-ui/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.)
      

################################################################
# General configuration variables for the TARBALL installation #
################################################################

INSTALL_ROOT=<the directory where you untar, e.g. $HOME/emi-ui>

###################################
# General configuration variables #
###################################

INSTALL_DIR=<usually the same of $INTALL_ROOT>
MY_DOMAIN=<your domain>

YAIM_LOGGING_LEVEL=DEBUG
USERS_CONF=${INSTALL_DIR}/emi-users.conf
GROUPS_CONF=${INSTALL_DIR}/emi-groups.conf
JAVA_LOCATION="/usr/java/latest"

################################
# Site configuration variables #
################################

SITE_NAME=<your site name>
SITE_EMAIL=devnull@freesurf.ch
           
PX_HOST=<myproxy server hostname>
WMS_HOST=<wms hostname>
BDII_HOST=<top level bdii hostname>
MON_HOST=<mon box hostname>
VOS="<list of supported VOS, e.g. dteam>"

QUEUES="dummy"
DUMMY_GROUP_ENABLE="dummy" 
CA_REPOSITORY="rpm http://linuxsoft.cern.ch/ 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>

An example of site-info.def could be found here: http://repo-pd.italiangrid.it/mrepo/ui-tar/....

If you would like to use other VOs have a look to the example file (./glite/yaim/examples/site-info.def) or visit the https://lcg-sft.cern.ch/yaimtool/yaimtool.py 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 Guide. In particular you might want to define the following variables:

      
DPM_HOST=my-dpm.cern.ch
LFC_HOST=my-lfc.cern.ch
RB_HOST=my-rb.cern.ch
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.

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 5.0.1 is contained in the tarball. Have a look at the user guide. For configuring the TAR_UI use the following command:

       cd ~/emi-ui
      ./glite/yaim/bin/yaim -c -s ./site-info.def -n UI_TAR
General remarks for the installation

Remember to source the file ${INSTALL_ROOT}/etc/profile.d/grid_env.(c)sh (this is not being done automatically).

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

     ./glite/yaim/bin/yaim -r -s ./site-info.def -n UI_TAR -f config_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.

EMI WN TAR

Introduction

We provide the EMI Worker Node as a tarball distribution. This distribution consists of one tarball containing the EMI software and external dependencies which are usually not installed on the host. The tarball version corresponds to the metapackage rpm version. The tarball also contains all the files needed for WN, thus it can be also used to install a WN into any directory.

Availabilty

A tarball distribution of the EMI-WN v. 1.0.0 is available on the following platforms

* SL5_x86_64 - http://emisoft.web.cern.ch/emisoft/dist/EMI/testing/1/sl5/x86_64/tgz/emi-wn-1.0.0-2.sl5-x86_64.tar.gz

Installation

Have a look at the README which contains information about WN versions. The tarball contains a file ${INSTALL_ROOT}/content.txt with information about the rpms contained therein.

Create a directory for the middleware, e.g. ~/emi-wn :

      cd
      mkdir emi-wn
Install the tarball in this directory
       cd ~/emi-wn
       wget http://emisoft.web.cern.ch/emisoft/dist/EMI/testing/1/sl5/x86_64/tgz/emi-wn-1.0.0-2.sl5-x86_64.tar.gz
       tar -zxvf emi-wn-1.0.0-2.sl5-x86_64.tar.gz

Configuration

Create a site-info.def file emi-wn/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.)

################################################################
# General configuration variables for the TARBALL installation #
################################################################

INSTALL_ROOT=<the directory where you untar, e.g. $HOME/emi-ui>
FUNCTIONS_DIR=${INSTALL_ROOT}/glite/yaim/functions

###################################
# General configuration variables #
###################################

INSTALL_DIR=<usually the same of $INTALL_ROOT>
MY_DOMAIN=<your domain>

YAIM_LOGGING_LEVEL=DEBUG
USERS_CONF=${INSTALL_DIR}/emi-users.conf
GROUPS_CONF=${INSTALL_DIR}/emi-groups.conf
WN_LIST=${INSTALL_DIR}/wn-list.conf
JAVA_LOCATION="/usr/java/latest"

################################
# Site configuration variables #
################################

SITE_NAME=<your site name>
SITE_EMAIL=devnull@freesurf.ch
           
PX_HOST=<myproxy server hostname>
WMS_HOST=<wms hostname>
BDII_HOST=<top level bdii hostname>
MON_HOST=<mon box hostname>
VOS="<list of supported VOS, e.g. dteam>"

QUEUES="dummy"
DUMMY_GROUP_ENABLE="dummy" 
CA_REPOSITORY="rpm http://linuxsoft.cern.ch/ 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>

An example of site-info.def could be found here: http://repo-pd.italiangrid.it/mrepo/...

If you would like to use other VOs have a look to the example file (./glite/yaim/examples/site-info.def) or visit the https://lcg-sft.cern.ch/yaimtool/yaimtool.py 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 Guide. In particular you might want to define the following variables:

      
DPM_HOST=my-dpm.cern.ch
LFC_HOST=my-lfc.cern.ch
RB_HOST=my-rb.cern.ch
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.

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 5.0.1 is contained in the tarball. Have a look at the user guide. For configuring the TAR_UI use the following command:

       cd ~/emi-wn
      ./glite/yaim/bin/yaim -c -s ./site-info.def -n WN_TAR

Torque client installation

The tarball does not include any batch system clients. Installing such clients on a WN usually requires root privileges. We provide here instructions on how to install the Torque batch system clients:

Remember to disable the dag.repo Download the epel and emi repository files:

# wget http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
# wget http://emisoft.web.cern.ch/emisoft/dist/EMI/1/sl5/x86_64/updates/emi-release-1.0.1-1.sl5.noarch.rpm
# yum localinstall epel-release-5-4.noarch.rpm emi-release-1.0.1-1.sl5.noarch.rpm
# yum install emi-torque-client
# cd ${INSTALL_ROOT}/glite/yaim/bin
# ./yaim -c -s site-info.def -n TORQUE_client

Creation of pool accounts

The function config_users can be used to create pool accounts on a TAR WN. Note that this function also creates a cron job cleanup-grid-accounts.

# cd ${INSTALL_ROOT}/glite/yaim/bin
# ./yaim -r -s site-info.def -n WN_TAR -f config_users

Installation of certificates

If you want YAIM to take care of the installation of the CA files, YAIM provides the following relevant functions config_certs_userland and config_crl:

config_certs_userland will install the CA files in the directory pointed by X509_CERT_DIR (providing that YAIM determines that valid CRL files are not already present in the directory). Be aware that the directory pointed by X509_CERT_DIR must exist and the user must have write permissions or otherwise YAIM will fail. The default value for X509_CERT_DIR is /etc/grid-security/certificates. If you want to use another location, redefine this variable in site-info.def and also define it in your shell's environment before starting yaim.

Remember that in case you don't use the standard location, you have to make sure you define X509_CERT_DIR and X509_VOMS_DIR in the pool accounts environment, since YAIM does not do this. In that case, edit the ${GLITE_EXTERNAL_ROOT}/etc/profile.d/grid-env.sh file and manually add:

gridenv_set  "X509_CERT_DIR" "your_non_standard_cert_path"
gridenv_set  "X509_VOMS_DIR" "your_non_standard_voms_path"

You can also edit the grid-clean-env.sh file to unset the same variables.

config_crl will create a cron job to maintain the crl files up to date.

The variable CA_REPOSITORY may be used to change the repository from which the CA files are fetched. The variable is defined by default in YAIM. Check the site-info.pre section for more information. In general this variable can be defined by the user if another repository is used.

Having set CA_REPOSITORY run the config_certs_userland and config_crl functions

# cd ${INSTALL_ROOT}/glite/yaim/bin
# ./yaim -r -s site-info.def -n WN_TAR -f config_certs_userland -f config_crl
The externals tarball contains VOMS server certifcates in ${GLITE_EXTERNAL_ROOT}/etc/grid-security/vomsdir. However, the function config_vomsdir is going to be introduced to create the .lsc files substituting the VOMS server certificates when bug 42943 is fixed.

Set up of the pool account environment

In ${GLITE_EXTERNAL_ROOT}/etc/profile.d you find scripts that should be sourced by every pool account. Either copy them to /etc/profile.d or create symlinks.

Note on wn-info.conf configuration

If you want to configure only once a TAR WN for a certain group of WNs, they should all belong to the same subcluster. Otherwise, /etc/glite-wn-info.conf will be overwritten. So in case you have more than one subcluster, you would need different TAR WNs to be installed in different places and to be configured independently.

Edit | Attach | PDF | History: r11 < r10 < r9 < r8 < r7 | Backlinks | Raw View | More topic actions
Topic revision: r11 - 2012-04-22 - CristinaAiftimiei
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback