File: Using_MPICH_In_Amazon_EC2.md

package info (click to toggle)
mpich 4.3.2-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 101,184 kB
  • sloc: ansic: 1,040,629; cpp: 82,270; javascript: 40,763; perl: 27,933; python: 16,041; sh: 14,676; xml: 14,418; f90: 12,916; makefile: 9,270; fortran: 8,046; java: 4,635; asm: 324; ruby: 103; awk: 27; lisp: 19; php: 8; sed: 4
file content (125 lines) | stat: -rw-r--r-- 3,701 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
# Using MPICH In Amazon EC2

To run mpi programs on Amazon EC2, you first need to have an account to
Amazon Web Services (AWS). Assume you are familiar with AWS and you know
how to start/stop/terminate Amazon EC2 instances, you can follow the
following steps to run mpi programs within a single Amazon EC2 region or
cross regions.

## Running MPI in a Single Amazon EC2 Region

### Install MPI in your cluster

Start a MPI cluster using Amazon EC2 instances. Make sure MPICH is
properly installed in your cluster. You can download MPICH here
(http://www.mpich.org/downloads/) and follow the following steps to
install.

```
tar -xzf mpich-3.2.tar.gz
cd mpich-3.2
./configure
make
sudo make install
```
If your build was successful, you should be able to see your installed
version by typing

```
mpiexec --version`
```

### Configure your MPI cluster

You should have a key pair, `yourkey.pem`, attached to the created instances.
First setup your environmental variables as follows. You can find the
access key and secret key in your Amazon EC2 account.

```
export AWS_ACCESS_KEY_ID=[ Your access key ]
export AWS_SECRET_ACCESS_KEY=[ Your access key secret ]
```
Try ssh to other instances in your cluster to make sure that your
environmental setup is successful.

```
ssh -i path-to-the-key/yourkey.pem username@other-instance-ip
```

To enable password-less ssh between instances, do the following for each
instance in your cluster.

```
cp path-to-the-key/yourkey.pem ~/.ssh/id_rsa
```

Then you should be able to ssh by typing

```
ssh username@other-instance-ip
```

### Run MPI in your cluster

Save the ip addresses of instances in a file named `host_file`. You can
compile your mpi program and execute it as following.

```
mpicc mpi_example.c -o example
mpiexec -n 2 -f host_file ./example
```

## Running MPI across Multiple Amazon EC2 Regions

If you want to run your code across multiple cloud regions, some
modifications are required to enable network communications.

### Start your MPI cluster

Create instances in your preferred regions. Make sure the security groups
of your instances allow inbound data transfer from other cloud regions.
Install MPI as introduced above to all your cluster machines. In Amazon
EC2, you can create one instance installed with all required packages
and use the image of this instance to create other machines. This will
save you some efforts.

### Configuration

Say for example you want to execute in us east and us west regions. Note
that, now you should have two keys, each for one region. To enable
password-less ssh between instances in different regions, configure the
following files.

For instances in the us east region:

```
cp path-to-the-key/us-east-key.pem ~/.ssh/id_rsa
```

Concatenate the `\~/.ssh/authorized_key` files in both us east and us
west regions and scp the concatenated file to all instances.

```
scp -i path-to-the-key/us-west-key.pem username@us-west-instance-ip:~/.ssh/authorized_key ~/.ssh/authorized_key_uw
cat ~/.ssh/authorized_key_uw >> ~/.ssh/authorized_key
scp -i path-to-the-key/us-west-key.pem ~/.ssh/authorized_key username@us-west-instance-ip:~/.ssh/
```

For instances in the us west region:

```
cp path-to-the-key/us-west-key.pem ~/.ssh/id_rsa
```

### Run MPI in your cluster

Save the \*public\* ip addresses, usually in the form 52.19.100.32 (for
example) in your hostfile. Note, do not use the public DNS, which is
usually in the form ec2-54-100-1-1.cpmpute-1.amazonaws.com. You can run
your mpi program by typing:

```
mpiexec -localhost host_node_ip -n 2 -f host_file ./example
```

The `host_node_ip` is the public ip address of your master node.