http://www.huihoo.org/npact/mpiindex.htm
四、Running on a LINUX Workstation Cluster
To run FLUENT on a network of LINUX workstations, type the usual startup command
without a version (i.e., fluent), and then use the Select Solver panel (Figure 30.2.1) to
specify the parallel architecture and version information.
File ?!Run...
1. Under Versions, specify the 3D or 2D single- or double-precision version by turning
the 3D and Double Precision options on or off, and turn on the Parallel option.
2. Under Options, select the Socket message-passing library in the Communicator dropdown
list.
When you start ! the parallel network version, you must select Socket or Network
MPI (MPICH) in the Communicator drop-down list, unless the vendor MPI library
(described earlier in this section) supports clustering. If you keep the Default option,
one of the MPI parallel versions will start instead, and you will be unable to spawn
additional compute nodes.
3. Set the number of initial compute node processes to spawn on the host machine in
the Processes field. You can start with 1 or 0 nodes and spawn the rest later on, as
described in Section fluent help 30.3.1.
4. (optional) Specify the name of a fiele containing a list of machines, one per line, in
the Hosts File eld. If the number of Processes is set to 0, FLUENT will spawn a
compute node on each machine listed in the file.
5. Click the Run button to start the parallel network version.
If you prefer to start the parallel network version from the command line, you can type
fluent version -t1 -pnet
(to use the socket communicator) or
fluent version -t1 -pnmpi
(to use the network MPI communicator) to start the solver with 1 compute node on the
host workstation. You can then spawn additional processes on remote workstations using the Network Confguration panel, as described in Section 30.3.1.
You can type
fluent version -t0 -pnet [-cnf=hostsfile]
(to use the socket communicator) or
fluent version -t0 -pnmpi [-cnf=hostsfile]
(to use the network MPI communicator) to start a host process that controls compute
nodes situated on remote machines. If the optional -cnf=hostsfile is specified, a compute node will be spawned on each machine listed in the file hostsfile. (If you enter this optional argument, do not include the square brackets.) Otherwise, you can spawn the processes as described in Section 30.3.1.