PAR Technologies V5 Installation via RPM packages, Getting the ParaStation5 RPM packages, Man

Page 11

Installation via RPM packages

man

contains the manual pages describing the ParaStation daemons, utilities and configuration files after installing the documentation package. The necessary steps are described in Section 3.4, “Installing the documentation”.

In order to enable the users to access these pages using the man(1) command, please consult the corresponding documentation 2.

mpi2, mpi2-intel, mpi2-pgi, mpi2-psc

contains an adapted version of MPIch2 after installing one of the various psmpi2 RPM files. The necessary steps are described in Section 3.5, “Installing MPI”.

Especially the sub-directories mpich/bin, mpich-intel/bin, etc, contain all the commands to run (mpirun) and compile (mpicc, mpif90, ...) parallel tasks.

All ParaStation5 specific kernel modules are located within the directory /lib/modules/ kernel release/kernel/drivers/net/ps4.

3.3. Installation via RPM packages

The recommended way to install ParaStation5 is the installation of packages using the rpm command. This is the preferred method on all SuSE or Red Hat based systems.

Getting the ParaStation5 RPM packages

Packages containing the different parts of the ParaStation5 system can be obtained from the download section of the ParaStation homepage.

At least two packages are needed, one containing the management part, the other one providing the communication part of the ParaStation5 system. Beside this core system, packages supplying MPIch for GNU, Intel, Portland Group and Pathscale compilers are available. A documentation package is also obtainable.

The full names of the RPM files follow a simple structure:

name-x.y.z-n.arch.rpm

where name denotes the name and thus the content of the packet, x.y.z describes the version number, n the build number and arch is the architecture, i.e. one of i586, ia64, x86_64, ppc or noarch. The latter is used e.g. for the documentation packet.

The package called psmgmt holds the management part of ParaStation. This package is required for any installation of the ParaStation5 system, independent of the underlying communication platform.

The communication libraries and modules for ParaStation5 come with the pscom package. As explained, all filenames are followed by an individual version number, the build date and the architecture.

The versions available on the ParaStation homepage at a time are tested to work properly together. It's recommended to install always the corresponding package versions. If only a part of the installation should be updated (i.e. only the management part while keeping the communication part untouched) the corresponding release notes should be consulted in order to verify that the intended combination is supported.

The release notes of the different packages will either be found within the installation directory /opt/ parastation or on the download section of the ParaStation homepage.

2Usually this is either done by modifying the MANPATH environment variable or by editing the manpath(1) configuration file, which is /etc/manpath.config by default.

ParaStation5 Administrator's Guide

7

Image 11
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 Hardware InstallationPrerequisites Kernel version Directory structureSoftware Mpi2, mpi2-intel, mpi2-pgi, mpi2-psc Installation via RPM packagesGetting the ParaStation5 RPM packages ManFile Version Installing the RPMsCompiling the ParaStation5 packages from source ParaStation entries Installing the documentationEtc/init.d/xinetd reload # 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 templateHostname id HWType runJob starter accounter Enable optimized network drivers# /opt/parastation/bin/testconfig Testing the installation # /opt/parastation/bin/testnodes -np nodes # /opt/parastation/bin/psiadmin -s -c listParaStation5 pscom communication library Insight ParaStation5# cat /proc/sys/ps4/state/connections # echo 10 /proc/sys/ps4/state/ResendTimeoutDirectory /proc/sys/ps4/state Directory /proc/sys/ps4/local Controlling process placementExporting environment variables for a task Using the ParaStation5 queuing facilityUsing non-ParaStationapplications 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 node shown as down TroubleshootingProblem psiadmin returns error 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 Options PsiadminSynopsis Extended description Standard ErrorStandard Input Standard OutputAllproc cnt count ExitAll Load Count hw hwDown HardwareQuit RdpSummary max max 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 Logfile=file Configfile=fileDebug=level ? , --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 Delete P4tcpAdd 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 Testing # /opt/parastation/bin/psiadmin psiadmin add# chkconfig -a /etc/init.d/parastation 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