9.4. Launching with SSH
When launching Open MPI jobs in a non-scheduled environment,
is typically used to launch commands on remote nodes. As listed in
the quick start section,
successfully launching MPI applications with
ssh requires the
You must be able to non-interactively login — without entering a password or passphrase — to all remote nodes from all remotes nodes.
Open MPI’s executables must be findable (e.g., in your
Open MPI’s libraries must be findable (e.g., in your
SSH keys must be setup such that the following can be executed without being prompted for password or passphrase:
shell$ ssh othernode echo hello hello shell$
Consult instructions and tutorials from around the internet to learn how to setup SSH keys. Try Google search terms like “passwordless SSH” or “SSH key authentication”.
For simplicity, it may be desirable to configure your SSH keys
without passphrases. This adds some risk, however (e.g., if your SSH
keys are compromised). But it simplifies your SSH setup because you
will not need to use
ssh-agent. Evaluate the risk level you are
Open MPI uses a tree-based pattern to launch processes on remote nodes. This means that Open MPI must be able to non-interactively login — without being prompted for password or passphrase — to any node in the host list from any node in the host list.
It may not be sufficient to only setup an SSH key from the node
where you are invoking
mpirun to all other nodes.
If you have a shared
$HOME filesystem between your nodes, you can
setup a single SSH key that is used to login to all nodes.
9.4.2. Finding Open MPI executables and libraries
Once Open MPI is able to use
ssh to invoke executables on a remote
node, it must be able to find its helper executables and shared
libraries on that remote node.
If Open MPI is installed in a system-level folder (e.g., in
/usr/bin), Open MPI will likely be able to find its executables
and libraries on the remote node with no additional assistance.
If, however, Open MPI is installed into a path that is not searched by default, you will need to provide assistance so that Open MPI can find its executables and libraries.
For simplicity, it is strongly recommended that you install Open MPI in the same location on all nodes in your job. See the Installation location section for more details.
You can do this in one of two ways.
126.96.36.199. Use “prefix” behavior
“Prefix” behavior is only available with
mpirun; it is
not available via resource manager direct launch mechanisms.
However, this section is about using
ssh to launch MPI jobs,
which means that there is no resource manager, and therefore there
is no direct launch mechanism available.
When “prefix” behavior is enabled, Open MPI will automatically set the
$LD_LIBRARY_PATH on remote nodes before executing
Open MPI assumes that the installation
libdir are the same on the remote node as they
are on the local node. If they are not, then you should not use
the “prefix” behavior.
You can enable “prefix” behavior in one of three ways:
Use an absolute path name to invoke
shell$ $HOME/my-openmpi/bin/mpirun --hostfile my-hostfile.txt mpi-hello-world
Simply using the absolute path name to
mpiruntells Open MPI to enable “prefix” mode.
shell$ $HOME/my-openmpi/bin/mpirun --hostfile my-hostfile.txt \ --prefix $HOME/my-openmpi \ mpi-hello-world The ``-prefix`` option takes a single argument: the prefix path to use for the bindir and libdir on the remote node.
Configure Open MPI with
If Open MPI is built this way,
mpirunwill always enable “prefix” behavior.
188.8.131.52. Set the
LD_LIBRARY_PATH in your shell startup files
Consider the case where Open MPI was configured with:
shell$ ./configure --prefix=$HOME/my-openmpi ...
In this cause, Open MPI will be installed into
This path is almost certainly not in any system-default search paths,
so it must be added to the
Specifically: the goal is that the following non-interactive commands must be able to execute without error:
# First, ensure that this command returns the correct ompi_info # instance (i.e., $HOME/my-openmpi/bin/ompi_info). shell$ ssh remotenode which ompi_info /home/myusername/my-openmpi/bin/ompi_info # Next, ensure that you can run that ompi_info command without # error shell$ ssh remotenode ompi_info # ... lots of output ...
Ensure that you do not see any errors about libraries that cannot be found.
All shells have some kind of script file that is executed at login time perform environmental setup tasks. This startup file is the one that needs to be edited to:
Add Open MPI’s executable path (which is likely
$HOME/my-openmpi/binin this example) to the
Add Open MPI’s library path (which is likely
$HOME/my-openmpi/libin this example) to the
You probably want to add Open MPI’s libraries to the front of
$LD_LIBRARY_PATH to ensure that this Open MPI
installation’s files are found first.
Consult the manual page for your shell for specific details (some shells are picky about the permissions of the startup file, for example). The list below contains some common shells and the startup files that they read/execute upon login:
TODO This rendering sucks, but I couldn’t make it play nice with list-table, either. :-(
$HOME/.bashrcif it exists.
$HOME/.bash_profileif it exists, or
$HOME/.bash_loginif it exists, or
$HOME/.profileif it exists (in that order). Note that some Linux distributions automatically come with
$HOME/.bash_profilescripts for users that automatically execute
$HOME/.bashrcas well. Consult the bash man page for more information.
Non-interactive login: This shell does not execute any file automatically, so Open MPI will execute the
$HOME/.profilescript before invoking Open MPI executables on remote nodes
$HOME/.tcshrcif it exists,
$HOME/.cshrcif it does not
$HOME/.tcshrcif it exists,
$HOME/.cshrcif it does not, followed by