cluster:Worker/2012.1/node
Contents |
TORQUE client v.2.5.7
Prepare
- Operating system
- Scientific Linux version 5.6 64 bit
Configure the following settings for the host:
- UMD repo
- NFS-client
- Create Host Based Authentication for Torque server. See ssh auth
| Client for torque should be install on server for management torque |
administrator's script: prepare.sh
# install umd#clean oldrm /etc/yum.repos.d/UMD* /etc/yum.repos.d/epel*
wget http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
wget http://repository.egi.eu/sw/production/umd/1/sl5/x86_64/updates/umd-release-1.0.2-1.el5.noarch.rpm
rm -f epel-release-5-4.noarch.rpm umd-release-1.0.2-1.el5.noarch.rpm
yum install epel-release-5-4.noarch.rpm
yum install yum-prioritiesyum install umd-release-1.0.2-1.el5.noarch.rpm
sed -i -e "s/priority=.*/priority=5/g" /etc/yum.repos.d/UMD-1-base.repo
sed -i -e "s/priority=.*/priority=4/g" /etc/yum.repos.d/UMD-1-updates.repo
Install
- Install Torque-server with yum from umd repo
administrator's script: install.sh
yum -y install torque-client.x86_64
# the emi torque package can be used as well# yum install emi-torque-client
Configure
- Configure server name in /var/torque/server_name
- Copy munge key for torque communication from torque-server
administrator's script: configure.sh
BATCH_SERVER=dgiref-batch.fzk.deecho -e $BATCH_SERVER > /var/torque/server_name
scp $BATCH_SERVER:/etc/munge/munge.key /etc/munge/munge.key
chown munge.munge /etc/munge/munge.key
chown munge:munge /var/log/munge/munged.log*
Proceed
- Enable munge autoboot
administrator's script: proceed.sh
service munge restart
chkconfig munge on
Initial test
- Create test script
- Test submit job with qsub
- Check queue and trace job
administrator's script: test.sh
# Tryecho "
#!/bin/bashsleep 60"> test.sh
qsub -q dgiseq test.sh# to check supported queues:# ldapsearch -x -H ldap://<CE_FQDN>:2170 -b mds-vo-name=resource,o=grid#To detect the jobid:qstat -Qqstat -a#To check the jobtracejob <jobid>
Update
update - is mostly to install new
administrator's script: update.sh
yum -y update torque-client.x86_64
Maui client v.3.2.6p21
Prepare
It is required to install the Torque client before the maui scheduler packages. It is required to install the Torque client (version 2.1.6 or version 2.3.6 depending on the Torque server version) before the maui scheduler packages.
administrator's script: prepare.sh
#!/bin/bash# prepare maui#-> start routineREPO_URL="http://dgiref.d-grid.de/svn/dgiref/PROD/cf3/repl/repos/external/"
wget -O /etc/yum.repos.d/sl-dgiref.repo ${REPO_URL}/sl-dgiref.repo
#<- end routine
Install
To install Maui, the following RPMs are needed :
- maui
- maui-client
Install rpms from dgiref binary repository.
administrator's script: install.sh
#!/bin/bash# install maui client#-> start routine# Choose the OS architecture:# OS_arch="x86_64" # x86_64 for 64 bitOS_arch="i686" # i686 for 32 bit
# SL 4 installation:yum -y install maui-3.2.6p21-dgrid_snap.1224706197.2.${OS_arch} maui-client-3.2.6p21-dgrid_snap.1224706197.2.${OS_arch}
# SL 5 installation:yum -y install maui-3.2.6p21-snap.1234905291.5.el5.x86_64 maui-client-3.2.6p21-snap.1234905291.5.el5.x86_64
#<- end routine
Configure
Assign the torque server into /var/spool/maui/maui.cfg
administrator's script: configure.sh
#!/bin/bash# configure maui clientTORQUE_SERVER="dgiref-batch"
#-> start routineecho `sed -i "s/localhost/${TORQUE_SERVER}/g" /var/spool/maui/maui.cfg`
#<- end routine
Initial test
- test with diagnose command
administrator's script: test.sh
#!/bin/bash# MAUI can be tested withshowq
showstats -udiagnose -g#<- end routine