recommend (and are going to assume this from now on) that an admin (local) account is
available on all machines. (You can use the “System preferences→Accounts” to set up an
admin user on the clients and use “System preferences→Sharing” to enable remote
login). Make sure that all nodes have “local” in their network domain search by adding
“local” into the domain search in “System preferences→Network” We are using
references [3] and [6] for this description.
We will not be able to easily partition these instructions into client and server part as
commands rely on each other among all nodes.
1. On the S10.4: download LAM-MPI from [14], get the OS X installer version
(unfortunately it comes without Fortran support). Install it (click on it once
downloaded), and then copy the installer package to /NetCommon so it can be
installed on all other computers easily.
2. On all the C10.4-s: install LAM-MPI from /NetCommon
3. On all nodes: when a non-login interactive shell is invoked (something that
LAM-MPI does while booting) then /etc/profile is not parsed by bash but
~/.bashrc is. Thus we will need to create or modify ~/.bashrc (e.g., using
“emacs ~/.bashrc”) to include the following line (make sure admin account
is used):
export PATH=”$PATH:/usr/local/bin”
as LAM-MPI was directly installed into /usr/local.
4. On the S10.4: create a “hostfile.lam” file (e.g., “emacs hostfile.lam”) with
each line containing a name of a node (extended by cpu=2 if it has two or a
dual core CPU, cpu=4 for a quad-core). For example in our infrastructure’s
hostfile.lam is:
mmac-servr00.local cpu=2
mmac01.local
mmac02.local
mmac03.local
5. On the S10.4: open a terminal as admin; type: “ssh-keygen -t rsa”; use the
default key-pair name (id_rsa) and enter a password of your choosing. This
has created a key-pair in the “~admin/.ssh” directory. Copy id_rsa.pub from
.ssh to /NetCommon as authorized_keys2:
“
cp ~/.ssh/id_rsa.pub /NetCommon/authorized_keys2”.
6. On all the C10.4-s: open a terminal window as admin (or log in from the
server using ssh: “
ssh admin@cmsl-mmac01”). Make sure you have a .ssh
directory, if you do not then use ssh to log into the same computer:
(“
ssh localhost”). Copy authorized_keys2 into .ssh:
“cp /NetCommon/authorized_keys2 ~/.ssh”. With the above steps we
have shared a public/private key-pair among nodes that is going to be essential
a little later.
7. (S10.4) To be able to boot LAM-MPI you will need to have an ssh-agent
running that can tell your login ssh to read the private key that we have
created above. Thus (and each time you need to set up LAM-MPI), open a
terminal window and type: “
ssh-agent –s”. This will output two lines of
Comentarios a estos manuales