User Manual

HPC FeaturesRev 2.1-1.0.6
Mellanox Technologies
118
Step 3. Check the public key.
Step 4. Now you need to add the public key to the authorized_keys2 file on the target machine.
For a local machine, simply add the key to
authorized_keys2.
Step 5. Test.
5.2.3 MPI Selector - Which MPI Runs
Mellanox OFED contains a simple mechanism for system administrators and end-users to select
which MPI implementation they want to use. The MPI selector functionality is not specific to
any MPI implementation; it can be used with any implementation that provides shell startup files
that correctly set the environment for that MPI. The Mellanox OFED installer will automatically
add MPI selector support for each MPI that it installs. Additional MPI's not known by the Mella-
nox OFED installer can be listed in the MPI selector; see the mpi-selector(1) man page for
details.
Note that MPI selector only affects the default MPI environment for future shells. Specifically, if
you use MPI selector to select MPI implementation ABC, this default selection will not take
effect until you start a new shell (e.g., logout and login again). Other packages (such as environ-
ment modules) provide functionality that allows changing your environment to point to a new
MPI implementation in the current shell. The MPI selector was not meant to duplicate or replace
that functionality.
The MPI selector functionality can be invoked in one of two ways:
1. The mpi-selector-menu command.
This command is a simple, menu-based program that allows the selection of the system-wide MPI
(usually only settable by root) and a per-user MPI selection. It also shows what the current selections
are. This command is recommended for all users.
2. The mpi-selector command.
This command is a CLI-equivalent of the mpi-selector-menu, allowing for the same functionality as
mpi-selector-menu but without the interactive menus and prompts. It is suitable for scripting.
-rw-r--r-- 1 root root 404 Mar 5 04:57 id_rsa.pub
host1$ cat id_rsa.pub
ssh-rsa
AAAAB3NzaC1yc2EAAAABIwAAAQEA1zVY8VBHQh9okZN7OA1ibUQ74RXm4zHeczyVxpYHaDPyDmqezbYMKrCIVz
d10bH+ZkC0rpLYviU0oUHd3fvNTfMs0gcGg08PysUf+12FyYjira2P1xyg6mkHLGGqVutfEMmABZ3wNCUg6J2X
3G/uiuSWXeubZmbXcMrP/
w4IWByfH8ajwo6A5WioNbFZElbYeeNfPZf4UNcgMOAMWp64sL58tkt32F+RGmyLXQWZL27Synsn6dHpxMqBorX
NC0ZBe4kTnUqm63nQ2z1qVMdL9FrCma1xIOu9+SQJAjwONevaMzFKEHe7YHg6YrNfXunfdbEurzB524TpPcrod
ZlfCQ== <username>@host1
host1$ cat id_rsa.pub | xargs ssh host2 \"echo >>/home/<username>/.ssh/
authorized_keys2"
<username>@host2's pass-
word: // Enter password
host1$
host1$ cat id_rsa.pub >> authorized_keys2
host1$ ssh host2 uname
Linux