PAR Technologies V5 manual Installing MPI, Further steps, # rpm -Uv psdoc-5.0.0-1.noarch.rpm

Page 14

Installing MPI

# rpm -Uv psdoc-5.0.0-1.noarch.rpm

All the PDF and HTML files will be installed within the directory /opt/parastation/doc, the manual pages will reside in /opt/parastation/man.

The intended starting point to browse the HTML version of the documentation is file:///opt/ parastation/doc/html/index.html.

The documentation is available in two PDF files called adminguide.pdf for the ParaStation5 Administrator's Guide and userguide.pdf for the ParaStation5 User's Guide. Both can be found in the directory /opt/parastation/doc/pdf.

In order to enable the manual pages to the users please consult the documentation of the man(1) command and the remark in Section 3.2, “Directory structure”, on how to do this.

3.5. Installing MPI

The standard for the implementation of parallel applications on distributed memory machines like clusters is MPI, the Message Passing Interface. In order to enable a ParaStation5 cluster for the development and execution of MPI programs, the installation of an adapted version of MPIch2 is necessary. A corresponding RPM packet can be found within the download section of the ParaStation homepage.

The corresponding package psmpi2 follows the common naming conventions of all ParaStation5 packets.

Beside the plain MPI package (psmpi2), which is compiled using the GNU gcc compiler, other versions of the MPI packet are available, which are built using different compilers like the PGI or Intel compilers on the Intel IA32 platform, the Intel compiler on the IA64 platform and the PGI, Intel and Pathscale compiler on X86_64 platform. These packets of course will depend on the corresponding compilers to be installed. Keep in mind that the use of this compilers might require further licenses.

After downloading the correct MPI package make sure to be root. In order to install MPIch for ParaStation5 from the rpm file, the command

# rpm -Uv psmpi2.5.0.0-1.i586.rpm

must be executed.

The command will extract the ParaStation5 MPI package to the directory /opt/parastation/mpi2.

In order to enable the MPI commands to the users make sure that the directory /opt/parastation/ mpi2/bin is included into the system wide PATH environment variable. Furthermore the administrator might want to enable the MPI manual pages for all users. These pages reside in /opt/parastation/ mpi2/man. Please consult the documentation of the man(1) command and the remark in Section 3.2, “Directory structure”on how to do this.

In general, all versions of ParaStation5 MPI supporting different compilers can be installed in parallel. The files will be copied to the directories /opt/parastation/mpi2 (for GNU gcc), /opt/parastation/ mpi2-intel(for Intel compiler) or /opt/parastation/mpi2-pgi(for Portland Group compiler), depending on the compiler version supported by the MPI package.

3.6. Further steps

The previous chapter described the basic installation of ParaStation5. There are still some steps to do, especially:

• configuration of the ParaStation5 system

10

ParaStation5 Administrator's Guide

Page 13 Page 15
Image 14
Page 13 Page 15
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 Hardware InstallationPrerequisites Kernel version Directory structureSoftware Man Installation via RPM packagesGetting the ParaStation5 RPM packages Mpi2, mpi2-intel, mpi2-pgi, mpi2-pscFile Version Installing the RPMsCompiling the ParaStation5 packages from source ParaStation entries Installing the documentationEtc/init.d/xinetd reload # 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 nodesHostname id HWType runJob starter accounter Enable optimized network drivers# /opt/parastation/bin/testconfig Testing the installation # /opt/parastation/bin/psiadmin -s -c list # /opt/parastation/bin/testnodes -np nodesInsight ParaStation5 ParaStation5 pscom communication library# cat /proc/sys/ps4/state/connections # echo 10 /proc/sys/ps4/state/ResendTimeoutDirectory /proc/sys/ps4/state Controlling process placement Directory /proc/sys/ps4/localExporting environment variables for a task Using the ParaStation5 queuing facilityUsing non-ParaStationapplications 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 node shown as down TroubleshootingProblem psiadmin returns error 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 Options PsiadminSynopsis Standard Output Standard ErrorStandard Input Extended descriptionAllproc cnt count ExitAll Hardware Count hw hwDown LoadQuit RdpSummary max max 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 Logfile=file Configfile=fileDebug=level 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 Delete P4tcpAdd 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 Testing # /opt/parastation/bin/psiadmin psiadmin add# chkconfig -a /etc/init.d/parastation 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
Top Page Image Contents