This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
cluster:102 [2011/06/29 11:08] hmeij |
cluster:102 [2011/06/29 11:29] hmeij |
||
---|---|---|---|
Line 11: | Line 11: | ||
< | < | ||
+ | |||
[root@petaltail ~]# host flexstorage | [root@petaltail ~]# host flexstorage | ||
flexstorage.wesleyan.edu has address 129.133.24.81 | flexstorage.wesleyan.edu has address 129.133.24.81 | ||
+ | |||
[root@petaltail ~]# df -h / | [root@petaltail ~]# df -h / | ||
Filesystem | Filesystem | ||
flexstorage.wesleyan.edu:/ | flexstorage.wesleyan.edu:/ | ||
| | ||
+ | |||
+ | </ | ||
+ | |||
+ | Host petaltail has the following interfaces. | ||
+ | |||
+ | < | ||
+ | |||
+ | eth0 Link encap: | ||
+ | inet addr: | ||
+ | eth1 Link encap: | ||
+ | inet addr: | ||
+ | eth2 Link encap: | ||
+ | inet addr: | ||
+ | eth3 Link encap: | ||
+ | inet addr: | ||
+ | |||
+ | </ | ||
+ | |||
+ | But a compute node on our cluster, for example node b1, has the following interfaces, all private | ||
+ | |||
+ | < | ||
+ | |||
+ | eth0 Link encap: | ||
+ | inet addr: | ||
+ | eth1 Link encap: | ||
+ | inet addr: | ||
+ | |||
+ | </ | ||
+ | |||
+ | So in order to for the compute node b1 to reach the flexstorage server we need to use NAT rules and define a path/ | ||
+ | |||
+ | < | ||
+ | |||
+ | *nat | ||
+ | # fss public to 10.10 | ||
+ | -A POSTROUTING -o eth2 -j MASQUERADE | ||
+ | COMMIT | ||
+ | |||
+ | *filter | ||
+ | # fss public via 10.10 | ||
+ | -A FORWARD -i eth1 -o eth2 -m state --state RELATED, | ||
+ | ... | ||
+ | COMMIT | ||
+ | |||
+ | </ | ||
+ | |||
+ | Next, on the compute nodes we need to add routing path and then mount the file system (using an IP because there is no name resolving). | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
</ | </ |