Generic debian cluster 26
From GBWiki
Contents |
Phenyx packages
System Setup
Add the following line (URL of the Phenyx repository) in /etc/apt/sources.list.d/phenyx.list file:
deb http://downloads.phenyx-ms.com/distrib/2.6/stable/debian-generic ./
Type the following command in a UNIX shell as root user. This command will do a System update ( update of the local package index files):
apt-get update
Binaries package Installation
Type the following commands in a UNIX shell as root. It will install the binaries Phenyx packages:
apt-get install phenyx-engine phenyx-engine-mpich
Cluster communication setup
ssh
phenyx user must be able to ssh from the master to the nodes without entering a password. This can be done by sharing public key.
Master public key generation
On the master, if ~phenyx/.ssh/id_dsa.pub file does not exist (you must be phenyx user to open ~phenyx/.ssh directory), do the following:
su - phenyx ssh-keygen -t dsa [double enter] cat $HOME/.ssh/id_dsa.pub [copy the content of the file in the clipboard]
Distribute the public key on the nodes
On each cluster node, as user phenyx
mkdir $HOME/.ssh/ cat >$HOME/.ssh/authorized_keys2 [the contents of the clipboard] ^D chmod 600 $HOME/.ssh/authorized_keys2
Make a first connection
For each node ($node), we need to make an initial connection from the master.
On the master, login as phenyx
ssh $node [answer yes if needed] logout
Batch system
Edit the nodes list
The simplest batch configuration is to use one resource queue with all the nodes. However, if one node can be multi-core or multi-processor. So we'll need to duplicate the node name as many times as we want process to be launched on this node (e.g. if a slave bi-pro dual core is to be used at maximum, we'll need to add 4 times this node name in the nodes list
- Open http://yourhost:8080/setup
- Manage parallel setup -> details
- Edit node list
- Save
And now your cluster is ready to make you job run!
