PAR Technologies V5 manual Directory structure, Software, Kernel version

Page 10

Software

Software

ParaStation requires a RPM-based Linux installation, as the ParaStation software is based on installable RPM packages.

All current distributions from Novell and Red Hat are supported, like

SuSE Linux Enterprise Server (SLES) 9 and 10

SuSE Professional 9.1, 9.2, 9.3 and 10.0, OpenSuSE 10.1, 10.2, 10.3

Red Hat Enterprise Linux (RHEL) 3, 4 and 5

Fedora Core, up to version 7

For other distributions and non-RPM based installations, please contact <support@par-tec.com>.

In order to use highspeed networks, additional libraries and kernel modules may be required. These packages are typically provided by the hardware vendors.

Kernel version

Using only TCP as a high speed interconnect protocol, no dedicated kernel modules are required. This is the ParaStation default communication path and is always enabled.

Using other interconnects and protocols, additional kernel modules are required. Especially using the optimized ParaStation p4sock protocol, a couple of additional modules are loaded. Refer to the section called “Installing the RPMs”for details. The ParaStation modules can be compiled for all major kernel versions within the 2.4 and 2.6 kernel streams.

Using InfiniBand and Myrinet requires additional modules and may restrict the supported kernels.

3.2. Directory structure

The default location to install ParaStation5 is /opt/parastation. Underneath this directory, several subdirectories are created containing the actual ParaStation5 installation:

bin

contains all executables and scripts forming the ParaStation system. This directory could be included into the PATH environment variable for easy access to the ParaStation administration tools.

config

contains the example configuration file parastation.conf.tmpl.

Depending on the communication part of the ParaStation system installed, more scripts and configuration files may be found within this directory.

doc

contains the ParaStation documentation after installing the corresponding RPM file. The necessary steps are described in Section 3.4, “Installing the documentation”.

include

contains the header files needed in order to build ParaStation applications. These files are primarily needed for building applications using the low level PSPort or PSE libraries.

These header files are not needed, if only MPI applications should be build or precompiled third party applications are used.

lib and lib64

contains various libraries needed in order to build and/or run applications using ParaStation and the ParaStation MPI libraries.

6

ParaStation5 Administrator's Guide

Image 10
Contents Administrators Guide ParaStation5 Administrators Guide Info@par-tec.comTable of Contents Problem different groups of nodes are seen as up or down Introduction History of ParaStationAbout this document Libraries Technical overviewRuntime daemon Kernel modulesLicense Prerequisites InstallationHardware Software Directory structureKernel version Man Installation via RPM packagesGetting the ParaStation5 RPM packages Mpi2, mpi2-intel, mpi2-pgi, mpi2-pscCompiling the ParaStation5 packages from source Installing the RPMsFile Version Etc/init.d/xinetd reload Installing the documentationParaStation entries # rpm -Uv psdoc-5.0.0-1.noarch.rpm Installing MPIFurther steps # rpm -Uv psmpi2.5.0.0-1.i586.rpmUninstalling ParaStation5 ParaStation5 Administrators Guide Copy template ConfigurationConfiguration of the ParaStation system Define Number of nodes# /opt/parastation/bin/testconfig Enable optimized network driversHostname id HWType runJob starter accounter Testing the installation # /opt/parastation/bin/psiadmin -s -c list # /opt/parastation/bin/testnodes -np nodesInsight ParaStation5 ParaStation5 pscom communication libraryDirectory /proc/sys/ps4/state # echo 10 /proc/sys/ps4/state/ResendTimeout# cat /proc/sys/ps4/state/connections Controlling process placement Directory /proc/sys/ps4/localUsing non-ParaStationapplications Using the ParaStation5 queuing facilityExporting environment variables for a task Controlling ParaStation5 communication paths Export LDPRELOAD=/opt/parastation/lib64/libp4tcp.soPSPP4S or PSPP4SOCK Authentication within ParaStation5Pspshm or Pspsharedmem Export PSPLIB=/opt/parastation/lib64/libpscomopenib.soParallel shell tool Homogeneous user ID spaceSingle system view Nodes and CPUsTok2env Integration with AFSIntegrating external queuing systems PSIRARGPRE0=/some/path/env2tokMulticasts # UseMCast Using ParaStation accountingCopying files in parallel Route add -net 224.0.0.0 netmask 240.0.0.0 dev ethXChanging the default ports for psid8 Using ParaStation process pinningUsing memory binding Spawning processes belonging to all groupsPort Problem psiadmin returns error TroubleshootingProblem node shown as down Problem different groups of nodes are seen as up or down Problem cannot start parallel taskProblem bad performance Problem cannot start process on frontendProblem pssh fails Problem psid does not startup, reports port in useProblem processes cannot access files on remote nodes Reference Pages ParaStation5 Administrators Guide Description InstallDir inst-dir , InstallationDir inst-dirParastation.conf ParametersStopscript SetupscriptStartscript StatusscriptMvapi P4sockOpenib ElanAccounter NrOfNodes numNode node17 16 HWType ethernet p4sock starter yes runJobs no $GENERATE 1-96 node$0,2 $0LogLevel num SelectTime timeDeadInterval num MCastGroup group-numDataSize size Core sizeCPUTime time MemLock sizeProc Processes maxprocs CPUmap mapRdpClosedTimeout ms RdpTimeout msStatusTimeout ms RdpResendTimeout msErrors See alsoParaStation5 Administrators Guide Synopsis PsiadminOptions Standard Output Standard ErrorStandard Input Extended descriptionAll ExitAllproc cnt count Hardware Count hw hwDown LoadSummary max max RdpQuit Group nodes Accounters nodesUser nodes Maxproc nodesHandleOldBins nodes Master nodesFreeOnSuspend nodes NodesSort nodesCpumap nodes Rlrss nodesRdpClosedTimeout nodes RdpTimeout nodesStatusTimeout nodes RdpResendTimeout nodesResolve nodes Restart nodesSelecttime time nodes Psiddebug mask nodesPattern Name Description HandleOldBins 0 1 nodes Rdpmaxretrans val nodes RdpClosedTimeout ms nodes RdpTimeout ms nodesStatusTimeout ms nodes RdpResendTimeout ms nodesNormal FilesQuiet VerbosePsid Debug=level Configfile=fileLogfile=file Num TestconfigFilename ? , --usage Show a help messageParaStation5 Administrators Guide Cnt num TestnodesNp num MapParaStation5 Administrators Guide Testpse Testpse -npnumParaStation5 Administrators Guide Net P4statSock ?,--helpParaStation5 Administrators Guide Add P4tcpDelete ParaStation5 Administrators Guide Psaccounter Pattern Description?, --help DumpcoreCoredir=dir Var/account/yyyymmdd Accounting files, one per dayPsaccview Lg,--ltotgroup Lj,--ljobsLu,--ltotuser Ls,--ltotsumCputime CpuweightAqtime EndInitialization 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 Appendix C. Upgrading ParaStation4 to ParaStation5 Building and installing ParaStation5 packages# psiadmin -s Changes to the runtime environmentPage Glossary ARPSee ParaStation Logger To share a common address space within a node ParaStation5 Administrators Guide