|
Size: 3692
Comment:
|
Size: 4639
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
<<TableOfContents>> |
|
| Line 5: | Line 7: |
| === From binary packages === | === Binary Distribution === |
| Line 7: | Line 9: |
| Binary packages for MPI-Start are generated using [[http://eu-etics.org/ |ETICS]]. Check their repositories for the correct package for your distribution. | Binary packages for mpi-start are generated in EMI using [[http://eu-etics.org/ |ETICS]]. Check EMI repositories for the correct package for your distribution. Once you have the repositories configured you only need to install the package using your favorite package manager: |
| Line 9: | Line 11: |
| === From source === | For RedHat based distributions: {{{ yum install mpi-start }}} |
| Line 11: | Line 16: |
| Source can be retrieved from the [[http://devel.ifca.es/hg/mpi-start/ |mercurial repository]] | Debian based: {{{ apt-get install mpi-start }}} |
| Line 13: | Line 21: |
| Installation is as easy as "make install". The default installation prefix is "/opt/i2g", by default it also creates files in /etc/profile.d. After the installation the environment variable I2G_MPI_START must be set to point to mpi-start script. | If you are running a gLite site, you may prefer to install the glite-mpi meta-package that includes the yaim plugin for configuraton. Information about this package is available at [[../MpiUtils | MPI-Utils]] {{{ yum install glite-mpi }}} |
| Line 15: | Line 26: |
| export I2G_MPI_START=/opt/i2g/bin/mpi-start | The nodes where the user applications will be executed (Worker Nodes) also require a working MPI implementation, Open MPI and MPICH are recommended. The devel packages should also be installed in order to allow user to compile their applications. Refer to your OS repositories for the exact packages. In the case of SL5, Open MPI (including devel packages) can be installed with the following command line: {{{ yum install openmpi openmpi-devel }}} {{{#!wiki caution '''devel packages and compilers''' Some devel packages of the MPI packages do not include the compiler as (e.g. gcc, gcc-gfortran, gcc-g++) dependency! They should be installed also if you want to support the compilation of MPI applications. }}} === Source Distribution === Source can be retrieved from the [[http://devel.ifca.es/hg/mpi-start/|mercurial repository]]. Installation is as easy as "make install". The default installation prefix is "/usr", by default it also creates files in /etc/profile.d. If a non default installation wants to be done, use the PREFIX variable in make install {{{ $ make install PREFIX=/opt/mpi-start }}} In this case, is recommendable setting the installation the environment variable `I2G_MPI_START` to point to mpi-start script (although this is not mandatory anymore). {{{ $ export I2G_MPI_START=/opt/mpi-start/bin/mpi-start }}} |
| Line 20: | Line 60: |
| MPI-Start is designed to auto detect most of the site configurations without any administrator intervention. The default installation will automatically detect: * the batch scheduler at the site: currently PBS/Torque, SGE, LSF and Slurm are supported. |
=== yaim configuration === There is a yaim plugin available for configuring gLite sites, check the documentation at [[../MpiUtils | MPI-Utils page]]. === Manual Configuration === mpi-start is designed to auto detect most of the site configurations without any administrator intervention. The default installation will automatically detect: * the batch scheduler at the site: currently PBS/Torque, SGE, LSF, Condor and Slurm are supported. |
| Line 28: | Line 73: |
| || ''Variable'' || ''Meaning'' || || '''MPI_DEFAULT_FLAVOUR''' || name of the default flavour for jobs running at the site || || '''MPI_<flavour>_PATH''' || Path of the bin and lib directories for the MPI flavour || || '''MPI_<flavour>_VERSION''' || '''FIXME''' preferred version of the MPI flavour ?? || || '''MPI_<flavour>_MPIEXEC''' || Path of the MPIEXEC binary for the specific flavour, takes precedence over other methods || || '''MPI_<flavour>_MPIEXEC_PARAMS''' || Parameters for the MPIEXEC of the flavour || || '''MPI_<flavour>_MPIRUN''' || Path of the MPIRUN binary for the specific flavour || || '''MPI_<flavour>_MPIRUN_PARAMS''' || Parameters for the MPIRUN of the flavour || || '''I2G_<flavour>_PREFIX''' || Path of the MPI installation for the MPI flavour || |
|| '''Variable''' || '''Meaning''' || ||`MPI_DEFAULT_FLAVOUR` || name of the default flavour for jobs running at the site || ||`MPI_<flavour>_PATH` || Path of the bin and lib directories for the MPI flavour || ||`MPI_<flavour>_VERSION` || preferred version of the MPI flavour || ||`MPI_<flavour>_MPIEXEC` || Path of the MPIEXEC binary for the specific flavour || ||`MPI_<flavour>_MPIEXEC_PARAMS` || Parameters for the MPIEXEC of the flavour || ||`MPI_<flavour>_MPIRUN` || Path of the MPIRUN binary for the specific flavour || ||`MPI_<flavour>_MPIRUN_PARAMS` || Parameters for the MPIRUN of the flavour || ||`I2G_<flavour>_PREFIX` || Path of the MPI installation for the MPI flavour || |
| Line 38: | Line 83: |
| The `I2G_<flavour>_PREFIX` takes precedence over the other variables. If `MPI_<flavour>_MPIEXEC` or `MPI_<flavour>_MPIRUN` are not defined, MPI-Start will try to use the mpiexec or mpirun that are found in the current PATH. | A known issue with the setting of the I2G_<flavour>_PREFIX variable makes them useless, please use the MPI_<flavour>_PATH variable instead! |
| Line 40: | Line 85: |
| If `MPI_<flavour>_MPIEXEC` or `MPI_<flavour>_MPIRUN` are not defined, mpi-start will try to use the mpiexec or mpirun that are found in the current PATH. | |
| Line 42: | Line 88: |
| Hooks may change the behavior of mpi-start and provide additional features such as file distribution and configuration of compiler flags. Site admins can add their own hooks via the local hook mechanism. | |
| Line 43: | Line 90: |
| Hooks may change the behavior of MPI-Start and provide additional features such as file distribution and configuration of compiler flags. Site admins can add their own hooks via the local hook mechanism of the [[../UserDocumentation/HooksFramework|Hooks Framework]]. === File distribution === MPI-Start includes hooks for distributing the files needed for the execution of an application. By default it tries to find the most suitable method for copying the files, using shared filesystems whenever they are found. However, the filesystem detection may not work for all sites, or the shared filesystem may be in a different location to the execution path making it impossible for MPI-Start to detect its availability. Site admins can tune the file distribution method with the following variables: || ''Variable'' || ''Meaning'' || || '''MPI_START_SHARED_FS''' || If undefined, MPI-Start will try to detect a shared file system in the execution directory. If defined and equal to 1, MPI-Start will assume that the execution directory is shared between all hosts and will not try to copy files. Any other value will make MPI-Start assume that the execution directory is not shared. || || '''MPI_SHARED_HOME''' || If set to `yes` , MPI-Start will use the path defined in `MPI_SHARED_HOME_PATH` for copying the files and executing the application || || '''MPI_SHARED_HOME_PATH''' || Path to a shared directory || |
mpi-start includes hooks for distributing the files needed for the execution of an application. By default it tries to find the most suitable method for copying the files, using shared filesystems whenever they are found. However, the filesystem detection may not work for all sites, or the shared filesystem may be in a different location to the execution path making it impossible for mpi-start to detect its availability. Check [[../UserDocumentation/HooksFramework|Hooks Framework]] for more information. |
MPI-Start for site administrators
Contents
Installation
Binary Distribution
Binary packages for mpi-start are generated in EMI using ETICS. Check EMI repositories for the correct package for your distribution. Once you have the repositories configured you only need to install the package using your favorite package manager:
For RedHat based distributions:
yum install mpi-start
Debian based:
apt-get install mpi-start
If you are running a gLite site, you may prefer to install the glite-mpi meta-package that includes the yaim plugin for configuraton. Information about this package is available at MPI-Utils
yum install glite-mpi
The nodes where the user applications will be executed (Worker Nodes) also require a working MPI implementation, Open MPI and MPICH are recommended. The devel packages should also be installed in order to allow user to compile their applications. Refer to your OS repositories for the exact packages. In the case of SL5, Open MPI (including devel packages) can be installed with the following command line:
yum install openmpi openmpi-devel
devel packages and compilers
Some devel packages of the MPI packages do not include the compiler as (e.g. gcc, gcc-gfortran, gcc-g++) dependency! They should be installed also if you want to support the compilation of MPI applications.
Source Distribution
Source can be retrieved from the mercurial repository.
Installation is as easy as "make install". The default installation prefix is "/usr", by default it also creates files in /etc/profile.d. If a non default installation wants to be done, use the PREFIX variable in make install
$ make install PREFIX=/opt/mpi-start
In this case, is recommendable setting the installation the environment variable I2G_MPI_START to point to mpi-start script (although this is not mandatory anymore).
$ export I2G_MPI_START=/opt/mpi-start/bin/mpi-start
MPI-Start configuration
yaim configuration
There is a yaim plugin available for configuring gLite sites, check the documentation at MPI-Utils page.
Manual Configuration
mpi-start is designed to auto detect most of the site configurations without any administrator intervention. The default installation will automatically detect:
- the batch scheduler at the site: currently PBS/Torque, SGE, LSF, Condor and Slurm are supported.
- existence of shared file system in the job running directory
- availability of OSC mpiexec for PBS/Torque systems
- default mpi installations for SLC5.
If the automatic detection fails for any of these, the administrator can set the following configuration variables:
Variable |
Meaning |
MPI_DEFAULT_FLAVOUR |
name of the default flavour for jobs running at the site |
MPI_<flavour>_PATH |
Path of the bin and lib directories for the MPI flavour |
MPI_<flavour>_VERSION |
preferred version of the MPI flavour |
MPI_<flavour>_MPIEXEC |
Path of the MPIEXEC binary for the specific flavour |
MPI_<flavour>_MPIEXEC_PARAMS |
Parameters for the MPIEXEC of the flavour |
MPI_<flavour>_MPIRUN |
Path of the MPIRUN binary for the specific flavour |
MPI_<flavour>_MPIRUN_PARAMS |
Parameters for the MPIRUN of the flavour |
I2G_<flavour>_PREFIX |
Path of the MPI installation for the MPI flavour |
A known issue with the setting of the I2G_<flavour>_PREFIX variable makes them useless, please use the MPI_<flavour>_PATH variable instead!
If MPI_<flavour>_MPIEXEC or MPI_<flavour>_MPIRUN are not defined, mpi-start will try to use the mpiexec or mpirun that are found in the current PATH.
Hooks
Hooks may change the behavior of mpi-start and provide additional features such as file distribution and configuration of compiler flags. Site admins can add their own hooks via the local hook mechanism.
mpi-start includes hooks for distributing the files needed for the execution of an application. By default it tries to find the most suitable method for copying the files, using shared filesystems whenever they are found. However, the filesystem detection may not work for all sites, or the shared filesystem may be in a different location to the execution path making it impossible for mpi-start to detect its availability. Check Hooks Framework for more information.