cluster:Worker/2/mpi
Contents |
Worker/2/mpi
Prepare
Configuration is necessary on both the CEs (gLite) and WNs in order to support and advertise MPI correctly (see Site configuration for MPI for details). This is performed by the gLite YAIM module glite-yaim-mpi which should be run on both the CE and WNs.
administrator's script: prepare.sh
#!/bin/bash# prepare mpi on wn#-> start routineyum -y install torque-devel-2.3.6 glite-yaim-mpi
yum -y install gcc-c++ compat-gcc-32 compat-gcc-32-c++
#<- end routine
Install
The following packages to install:
-
openmpi -
MPI-START
administrator's script: install.sh
#!/bin/sh# install MPI packages#-> start routinerpm install --prefix=/opt/glite-mw/openmpi-1.2.9 http://mirror.scc.kit.edu/downloads/rpms/wns/2010.1/openmpi-1.2.9-1.x86_64.rpm
yum -y install --prefix= /opt/glite-mw/i2g http://mirror.scc.kit.edu/downloads/rpms/wns/2010.1/i2g-mpi-start-0.0.58-1
#<- end routine
Configure
- Add the following to the site-info.de of the CE and WNs. see YaimConfig for detailed information.
- export set of environment variables to avoid
INFO: No MPI flavours enabled. - execute yaim command to configure
WARNING: in /etc/hosts you have to set wn with full hostname, otherwise yaim wont't find hostname -f:hostname wn.fzk.de and the yaim will abort the configuration!!!
After yaim configuration has finished edit /etc/hosts again with wn older hostname, other wise the node will be seen twice as different node wn and wn.fzk.de while reserving nodes for an MPI job.!!!
administrator's script: configure.sh
#!/bin/bash# configure mpi on wns#-> start routinecat /opt/glite-mw/site-info.de
MPI_OPENMPI_ENABLE="yes"
MPI_OPENMPI_PATH="/opt/glite-mw/openmpi-1.2.9"
MPI_OPENMPI_VERSION="1.2.9"
MPI_SHARED_HOME="yes"
MPI_SSH_HOST_BASED_AUTH="no"
I2G_MPI_START="$INSTALL_ROOT/i2g/bin/mpi-start"
# export environment variablesexport MPI_OPENMPI_VERSION="1.2.9"
export MPI_OPENMPI_PATH="/opt/glite-mw/openmpi-1.2.9"
export MPI_OPENMPI_ENABLE="yes"
# execute yaim command/opt/glite-mw/glite/yaim/bin/yaim -c -s site-info.def -n MPI_WN -n WN_TAR -n TORQUE_client
#<- end routine
Initial test
- You can try submitting a job to your site using the instructions found via the page job submission
- You can do some basic tests by logging in on a WN as a pool user and running the following:
administrator's script: test.sh
#!/bin/bash# initial test mpiUSER='griduser'
su $USER
env|grep MPI_
# Result should be:# MPI_MPICC_OPTS=-m32# MPI_SSH_HOST_BASED_AUTH=yes# MPI_OPENMPI_PATH=/opt/openmpi/1.1# MPI_LAM_VERSION=7.1.2# MPI_MPICXX_OPTS=-m32# MPI_LAM_PATH=/usr# MPI_OPENMPI_VERSION=1.1# MPI_MPIF77_OPTS=-m32# MPI_MPICH_VERSION=1.2.7# MPI_MPIEXEC_PATH=/opt/mpiexec-0.80# MPI_MPICH2_PATH=/opt/mpich2-1.0.4# MPI_MPICH2_VERSION=1.0.4# I2G_MPI_START=/opt/i2g/bin/mpi-start# MPI_MPICH_PATH=/opt/mpich-1.2.7p1exit 0