PAR Technologies V5 manual Node node17 16 HWType ethernet p4sock starter yes runJobs no

Page 43

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-entryor runJobs-entrymay 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.

ParaStation5 Administrator's Guide

39

Image 43
Contents Administrators Guide Info@par-tec.com ParaStation5 Administrators GuideTable of Contents Problem different groups of nodes are seen as up or down History of ParaStation IntroductionAbout this document Kernel modules Technical overviewRuntime daemon LibrariesLicense Prerequisites InstallationHardware Software Directory structureKernel version Mpi2, mpi2-intel, mpi2-pgi, mpi2-psc Installation via RPM packagesGetting the ParaStation5 RPM packages ManCompiling the ParaStation5 packages from source Installing the RPMsFile Version Etc/init.d/xinetd reload Installing the documentationParaStation entries # rpm -Uv psmpi2.5.0.0-1.i586.rpm Installing MPIFurther steps # rpm -Uv psdoc-5.0.0-1.noarch.rpmUninstalling ParaStation5 ParaStation5 Administrators Guide Define Number of nodes ConfigurationConfiguration of the ParaStation system Copy template# /opt/parastation/bin/testconfig Enable optimized network driversHostname id HWType runJob starter accounter Testing the installation # /opt/parastation/bin/testnodes -np nodes # /opt/parastation/bin/psiadmin -s -c listParaStation5 pscom communication library Insight ParaStation5Directory /proc/sys/ps4/state # echo 10 /proc/sys/ps4/state/ResendTimeout# cat /proc/sys/ps4/state/connections Directory /proc/sys/ps4/local Controlling process placementUsing non-ParaStationapplications Using the ParaStation5 queuing facilityExporting environment variables for a task Export LDPRELOAD=/opt/parastation/lib64/libp4tcp.so Controlling ParaStation5 communication pathsExport PSPLIB=/opt/parastation/lib64/libpscomopenib.so Authentication within ParaStation5Pspshm or Pspsharedmem PSPP4S or PSPP4SOCKNodes and CPUs Homogeneous user ID spaceSingle system view Parallel shell toolPSIRARGPRE0=/some/path/env2tok Integration with AFSIntegrating external queuing systems Tok2envMulticasts Route add -net 224.0.0.0 netmask 240.0.0.0 dev ethX Using ParaStation accountingCopying files in parallel # UseMCastSpawning processes belonging to all groups Using ParaStation process pinningUsing memory binding Changing the default ports for psid8Port Problem psiadmin returns error TroubleshootingProblem node shown as down Problem cannot start process on frontend Problem cannot start parallel taskProblem bad performance Problem different groups of nodes are seen as up or downProblem psid does not startup, reports port in use Problem pssh failsProblem processes cannot access files on remote nodes Reference Pages ParaStation5 Administrators Guide Parameters InstallDir inst-dir , InstallationDir inst-dirParastation.conf DescriptionStatusscript SetupscriptStartscript StopscriptElan P4sockOpenib MvapiNrOfNodes num Accounter$GENERATE 1-96 node$0,2 $0 Node node17 16 HWType ethernet p4sock starter yes runJobs noMCastGroup group-num SelectTime timeDeadInterval num LogLevel numMemLock size Core sizeCPUTime time DataSize sizeProc CPUmap map Processes maxprocsRdpResendTimeout ms RdpTimeout msStatusTimeout ms RdpClosedTimeout msSee also ErrorsParaStation5 Administrators Guide Synopsis PsiadminOptions Extended description Standard ErrorStandard Input Standard OutputAll ExitAllproc cnt count Load Count hw hwDown HardwareSummary max max RdpQuit Maxproc nodes Accounters nodesUser nodes Group nodesNodesSort nodes Master nodesFreeOnSuspend nodes HandleOldBins nodesRlrss nodes Cpumap nodesRdpResendTimeout nodes RdpTimeout nodesStatusTimeout nodes RdpClosedTimeout nodesRestart nodes Resolve nodesPsiddebug mask nodes Selecttime time nodesPattern Name Description HandleOldBins 0 1 nodes Rdpmaxretrans val nodes RdpResendTimeout ms nodes RdpTimeout ms nodesStatusTimeout ms nodes RdpClosedTimeout ms nodesVerbose FilesQuiet NormalPsid Debug=level Configfile=fileLogfile=file ? , --usage Show a help message TestconfigFilename NumParaStation5 Administrators Guide Map TestnodesNp num Cnt numParaStation5 Administrators Guide Testpse -npnum TestpseParaStation5 Administrators Guide ?,--help P4statSock NetParaStation5 Administrators Guide Add P4tcpDelete ParaStation5 Administrators Guide Pattern Description PsaccounterVar/account/yyyymmdd Accounting files, one per day DumpcoreCoredir=dir ?, --helpPsaccview Ls,--ltotsum Lj,--ljobsLu,--ltotuser Lg,--ltotgroupEnd CpuweightAqtime CputimeInitialization file Mlisten ParaStation5 Administrators Guide Appendix A. Quick Installation Guide # chkconfig -a /etc/init.d/parastation # /opt/parastation/bin/psiadmin psiadmin addTesting Appendix B. ParaStation license Page Page Page Changes to the runtime environment Building and installing ParaStation5 packages# psiadmin -s Appendix C. Upgrading ParaStation4 to ParaStation5Page ARP GlossarySee ParaStation Logger To share a common address space within a node ParaStation5 Administrators Guide