Qlogic InfiniPath, Install Manual

Page: 65 / 74

IB0056101-00 C A-1
Appendix A
RPM Descriptions
The following sections show more detailed descriptions of the RPMs for InfiniPath
and OpenFabrics.
A.1
InfiniPath and OpenFabrics RPMs
For ease of installation, it is recommended that all RPMs are installed on all nodes.
However, some RPMs are optional. Since cluster nodes may be used for different
functions, it is possible to selectively install. An example would be the
opensm
package for use on the node which will act as a subnet manager. If you want to
selectively install the RPMs, see the following tables for a comparison of required
and optional packages.
A.2
Different Nodes May Use Different RPMs
In a cluster environment different nodes may be used for different functions, such
as launching jobs, software development, or running jobs. We define these nodes
in the following way:
■
Front end node . This node will launch jobs. It is referred to as the front end node
in this documentation.
■
Compute node . These are the nodes that are used to run jobs.
■
A development or build node . These are the machines on which examples or
benchmarks can be compiled.
Any machine can serve any combination of these three purposes, but a typical
cluster has many compute nodes and only one or just a few front end nodes. The
number of nodes used for development will vary. Although QLogic recommends
installing all RPMs on all nodes, not all InfiniPath software is required on all nodes.
See
Table A-1 for information on installation of software RPMs on specific types of
nodes. Note that each set of RPMs uses a build identifier
xxx
and a distribution
identifier
yyy
. The architecture is designated by
x86_64
,
noarch
,
i386
, or
ppc64
,
and is dependent upon the distribution.
The RPMs are now organized in the following way: