If the blog is not suitable, tell me where to moveFor programming "under the cluster," there is a certain set of technologies, which includes such grants as commercial Visual Studio, in the version 2010 of which Microsoft programmers carried out a huge amount of work, and the freely distributed Eclipse, which will be discussed.
So, for Eclipse, the development team is actively developing a bunch of PTP & PLDT, all the information about which can be found on the
site .
Notes for those interested:
* A compilation of a project on C is considered. A C ++ project is configured similarly. For Java, not tested.
* Guide for admin.
')
In short, before habrakata:
* Eclipse should be properly built with the necessary plugins (PTP & PLDT);
* MPI implementation should be compiled (in this case MPICH, but OpenMPI can also be used);
* MPICH will launch its daemon on compute nodes (including the head)
So, for the beginning we will collect the necessary software. We will work in Linux.
Beforehand, it is necessary to share on NFS the place from which the MPICH will be launched on all nodes. This is necessary because MPICH must run its daemon on all nodes.
wget
www.mcs.anl.gov/research/projects/mpich2/downloads/tarballs/1.2.1p1/mpich2-1.2.1p1.tar.gztar xvf mpich2-1.2.1p1.tar.gz
cd mpich2-1.1.1p1
./configure --prefix = / home / mpich
make
make install
Download Eclipse from eclipse.org, in this case Eclipse Galileo. We unpack in any place and we start.
Eclipse for working with a cluster uses the Parallel Tools Platform (PTP) + Parallel Language Development Tool (PLDT). We will install them using Help-> Install New Software.
Update site for PTP:
download.eclipse.org/tools/ptp/releases/galileoSelect the necessary options (and only PTP, PLDT and Support For MPICH2 are needed at this stage) and install the plugin. To finish configuring the plugin, you need to install a native debugger, which we do:
cd /distr/soft/eclipse/plugins/org.eclipse.ptp.linux.x86_64_3.0.1.201002011019
sh BUILD
If the debugger is installed (the bin subfolder appears), then proceed to the next step - setting MPICH2.
Create a .mpd.conf file and enter the secret word into it to organize the “ring” of MPICH2 daemons that will be used by the daemon from the nodes to connect to the demon on the head node
touch /etc/mpd.conf
Enter the word: MPD_SECRETWORD = someword
chmod 0700 /etc/mpd.conf
/ home / mpich / bin / mpd -n --daemon
/ home / mpich / bin / mpdtrace -l
Using mpdtrace, we get the port number on which our demon hangs. We will use it to form the “ring” MPICH2.
We decouple the file with the secret word on all nodes:
for i in `seq 1 []`; do scp /etc/.mpd.conf [name] $ i: / etc /; done;
Run the demons:
/ home / mpich / bin / mpd -h sblade -p [port shown by mpdtrace] --daemon
Check on the head node how the setup went:
sblade: ~ # / home / mpich / bin / mpdtrace -l 255 / pts / 5 [17:27:11]
sblade_44222 (192.168.101.101)
node2_33135 (192.168.101.2)
node3_43780 (192.168.101.3)
node1_36588 (192.168.101.1)
If so, then the configuration of Eclipse, MPICH and PTP is complete. For the administrator.