PAR Technologies PARASTATION5 V5 - Manual (Page 43)

ParaStation5 Administrator's Guide 39
Node[s] hostname id [HWType-entry] [starter-entry] [runJobs-entry] [env name value ] [env { name
value ... }]
Node[s] { { hostname id [HWType-entry] [starter-entry] [runJobs-entry] [env name value ] [env { name
value ... }] }... }
Node[s] $GENERATE from - to / step nodestr idstr [HWType-entry] [starter-entry] [runJobs-entry]
[env name value ] [env { name value ... }]
Define one or more nodes to be part of the ParaStation cluster.
This is the first example of a parameter that supports the environment mode. This means there are
two different notations to use this parameter. The first one may be used to define a single node, the
second one will allow to register more than one node within a single command. It is a convenient form
that prevents from typing the keyword once per entry again and again.
Each entry has to have at least two items, the hostname and the id . This will tell the ParaStation
system that the node called hostname will act as the physical node with ParaStation ID id .
hostname is either a resolvable hostname or an IP address in dot notation (e.g. 192.168.1.17). id is
an integer number in the range from 0 to NrOfNodes-1.
Further optional items as HWType-entry , starter-entry or runJobs-entry may overrule the
default values of the hardware type on the node, the ability to start parallel jobs from this node or the
possibility to run processes on this node respectively. These entries have the same syntax as the stand
alone commands to set the corresponding default value.
E.g. the line
Node node17 16 HWType { ethernet p4sock } starter yes runJobs no
will define the node node17 to have the ParaStation ID 16. Furthermore it is expected to have a
Ethernet communication using both TCP and p4sock protocols. It is allowed to start parallel tasks from
this node but the node itself will not run any process of any parallel task (except the ParaStation logger
processes of the tasks started on this node).
The option environment or env allows per node environment variables to be set. Using the first
form, the variable name is set to value . More then one name/value pair may be given. More complex
values may be given using quotation marks:
Node node17 16 environment LD_LIBRARY_PATH /mypath
Node node18 17 env { PSP_P4S "2" PSP_OPENIB "0" }
This example will define the variable LD_LIBRARY_PATH to /mypath for node node17 and the
variables PSP_P4S and PSP_OPENIB to 2 and 0 for node node18 .
The $GENERATE allows to define a group of nodes at once using a simple syntax. Using the parameters
from and to , a range may be defined, incremented by step . Each entry in this range may be
referenced within the nodestr and idstr using a syntax of $[{offset[,width[,base]]}] . Eg.,
the entry
$GENERATE 1-96 node${0,2} ${0}
define the nodes node01 up to node96 using the id's 1 - 96, respectively. More node specific attributes
may be defined as described above.
LicenseServer hostname , LicServer hostname
LicenseFile lic-file , LicFile lic-file
LicenseDeadInterval num , LicDeadInterval num
These entries are silently ignored by this version of ParaStation.