Installation of gLite Services

This guide focuses on the procedure of middleware installation and configuration for three main type of grid nodes, namely cream computing element (creamCE), storage element (SE) and worker node (WN). The required steps to install and to configure the gLite middleware version 3.2 are described.

The required OS for gLite middleware is Scientific Linux 5. A general requirement for the gLite nodes is that they are synchronised. The yum package manager is considered to be the default installation tool and is used to install some packages that are needed during the installation of the described node types. Therefore the following actions need to be performed:

 
#  yum update 
#  yum install chkconfig

//Node synchronisation
# yum install ntpdate
# service ntpd start
# chkconfig ntpd on
# ntpq -p 

// Network setup
# vi /etc/resolv.conf and replace the last line with  search one.ypepth.grnet.gr localdomain 

*It is important* for the installation and configuration of the various services to verify that hostname -f returns the correct hostname of the node.

// SELinux deactivation
# vi /etc/sysconfig/selinux 
   setenforce 0

# sestatus 


// Shut down of iptables
# /etc/init.d/iptables stop
# iptables -L -v
# chkconfig iptables off

For a successful installation, the package manager needs to be configured so as to reference a number of repositories (in addition to your OS), namely:

• the middleware repositories
• the CA repository
• DAG
• SL

During this step, the ce and se nodes need to have the IPs defined in the issued certificates. Moreover, some more packages depending on the node type are needed. Therefore, the following command need to be executed according to each node type:

CE Node

# yum install xml-commons-apis

# cd /etc/yum.repos.d/

# wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-CREAM.repo

# wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-TORQUE_server.repo

# wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-TORQUE_utils.repo

# wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-BDII.repo

# wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/lcg-CA.repo

For MPI support:

# wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-MPI_utils.repo

# cd
# yum --enablerepo='glite-*' install lcg-CA glite-BDII glite-CREAM  glite-TORQUE_server  glite-TORQUE_utils glite-MPI_utils

# mkdir /home/seeops

It is recommended to disable automatic updates by changing the corresponding parameter to enabled = 0 in the files * glite-CREAM.repo, glite-TORQUE_server.repo, glite-TORQUE_utils.repo, glite-BDII.repo, glite-MPI_utils.repo*, before installing the gLite packages.

SE node

# yum install mysql-server 

# cd /etc/yum.repos.d/

# wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/lcg-CA.repo

# wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-SE_dpm_mysql.repo

# cd
#  yum --enablerepo='glite-*' --enablerepo=dag install lcg-CA glite-SE_dpm_mysql

# mkdir /home/seeops

It is recommended to disable automatic updates by changing the corresponding parameter to enabled = 0 in the files *glite-SE_dpm_mysql.repo*, before installing the gLite packages.

WN node

# cd /etc/yum.repos.d/

# wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/lcg-CA.repo

# wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-WN.repo

# wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-TORQUE_client.repo

For MPI support:

# wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-MPI_utils.repo

# yum --enablerepo='glite-*' install lcg-CA

# yum --enablerepo='glite-*' groupinstall glite-WN

# yum --enablerepo='glite-*' install glite-TORQUE_client

For MPI support:

# yum --enablerepo='glite-*' install glite-MPI_utils

#  mkdir /home/seeops

It is also recommended to disable automatic updates by changing the corresponding parameter to enabled = 0 in the files * glite-WN.repo, glite-TORQUE_client.repo *, before installing the gLite packages.

The configuration of the middleware is executed with YAIM tool. The necessary YAIM modules needed to configure a certain node type are automatically installed with the middleware. Before configuring each service, the certificates of the ce and se needs to be placed in the directory /etc/grid-security/ and the appropriate files to change depending on the specific setup. The files to adapt are:

• /etc/hosts
• /opt/glite/yaim/etc/siteinfo/site-info.def
• /opt/glite/yaim/etc/siteinfo/vo.d/ops.vo.egee-see.org
• /opt/glite/yaim/etc/siteinfo/services/glite-bdii_site
• /opt/glite/yaim/etc/siteinfo/services/glite-creamce
• /opt/glite/yaim/etc/siteinfo/services/glite-se_dpm_mysql
• /opt/glite/yaim/etc/siteinfo/services/glite-se_dpm_disk
• /opt/glite/yaim/etc/groups.conf
• /opt/glite/yaim/etc/users.conf
• /opt/glite/yaim/etc/wn-list.conf

For each node type, the configuration is achieved by following the next steps:

CE Node

# /opt/glite/yaim/bin/yaim -c -s /opt/glite/yaim/etc/siteinfo/site-info.def -n creamCE -n TORQUE_server -n TORQUE_utils -n BDII_site

# /etc/init.d/pbs_server restart

# mv /opt/glite/var/info/ops.vo.egee-see.org /opt/edg/var/info/

SE Node

# /opt/glite/yaim/bin/yaim -c -s /opt/glite/yaim/etc/siteinfo/site-info.def -n SE_dpm_mysql

WN Node

# /opt/glite/yaim/bin/yaim -c -s /opt/glite/yaim/etc/siteinfo/site-info.def -n WN -n TORQUE_client

And now, the Grid site with CE, SE and WNs is ready!!!