Tags: , view all tags

Notes about Installation and Configuration of WN using Torque with MPI support - WORK IN PROGRESS

These notes are provided by site admins on a best effort base as a contribution to the IGI communities and MUST not be considered as a subsitute of the Official IGI documentation.
This document is addressed to site administrators responsible for middleware installation and configuration.
The goal of this page is to provide some hints and examples on how to install and configure an EMI WN + MPI service based on EMI middleware using TORQUE as batch system

References

Service installation

O.S. and Repos

O.S. and Repos

Starts from a fresh installation of Scientific Linux 5.x (x86_64).

# cat /etc/redhat-release 
Scientific Linux SL release 5.7 (Boron)

* Install the additional repositories: EPEL, Certification Authority, UMD

# yum install yum-priorities yum-protectbase
# cd /etc/yum.repos.d/
# rpm -ivh http://mirror.switch.ch/ftp/mirror/epel//5/x86_64/epel-release-5-4.noarch.rpm
# wget http://repo-pd.italiangrid.it/mrepo/repos/egi-trustanchors.repo
# rpm -ivh http://repo-pd.italiangrid.it/mrepo/EMI/1/sl5/x86_64/updates/emi-release-1.0.1-1.sl5.noarch.rpm
# wget http://repo-pd.italiangrid.it/mrepo/repos/igi/sl5/x86_64/igi-emi.repo

Be sure that SELINUX is disabled (or permissive). Details on how to disable SELINUX are here:

# getenforce 
Disabled

Check the repos list (sl-*.repo are the repos of the O.S. and they should be present by default).

# ls /etc/yum.repos.d/
egi-trustanchors.repo  
emi1-third-party.repo emi1-base.repo emi1-updates.repo
epel.repo epel-testing.repo  igi-emi.repo
sl-contrib.repo sl-fastbugs.repo sl-security.repo sl-testing.repo sl-debuginfo.repo sl.repo sl-srpms.repo

IMPORTANT: remove the dag repository if present

yum install

yum install

# yum clean all
Loaded plugins: downloadonly, kernel-module, priorities, protect-packages, protectbase, security, verify, versionlock
Cleaning up Everything

# yum install ca-policy-egi-core
# yum install igi-wn_torque_noafs 
# yum install glite-mpi 
# yum install emi-version
# yum install openmpi openmpi-devel
# yum install mpich2 mpich2-devel
# yum install nfs-utils

see here for details

Service configuration

You have to copy the configuration files in another path, for example root, and set them properly (see later):

# ls /opt/glite/yaim/examples/siteinfo/
services  site-info.def

# ls /opt/glite/yaim/examples/siteinfo/services/
glite-mpi  glite-mpi_ce  glite-mpi_sl4-x86  glite-mpi_sl5-x86_64  glite-mpi_wn  glite-vobox  glite-wn  glite-wn_tar  igi-mpi

# cp -r /opt/glite/yaim/examples/siteinfo/* .

keep and edit only these files:

# ls services/
glite-mpi  glite-mpi_ce  glite-mpi_wn

vo.d directory

vo.d directory

Create the vo.d directory for the VO configuration file (you can decide if keep the VO information in the site.def or putting them in the vo.d directory)

# mkdir vo.d

here an example for some VOs.

Information about the several VOs are available at the CENTRAL OPERATIONS PORTAL.

users and groups configuration

users and groups configuration

here an example on how to define pool accounts (ig-users.conf

) and groups (ig-groups.conf

) for several VOs

site-info.def

site-info.def

SUGGESTION: use the same site-info.def for CREAM and WNs: for this reason in this example file there are yaim variable used by CREAM, TORQUE or emi-WN.

It is also included the settings of some VOs

For your convenience there is an explanation of each yaim variable. For more details look at [6, 7, 8, 9]

-- AlessandroPaolini - 2012-04-23