C RPM Descriptions
The following sections contain detailed descriptions of the RPMs for InfiniPath and OpenFabrics software.
InfiniPath and OpenFabrics RPMs
For ease of installation, QLogic recommends that all RPMs are installed on all nodes. However, some RPMs are optional. Since cluster nodes can be used for different functions, it is possible to selectively install RPMs. For example, you can install the opensm package for use on the node that 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.
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. These nodes are defined as follows:
Front end node. This node launches jobs. It is referred to as the front end node throughout this document.
Compute node. These nodes run jobs.
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 just a few (or only one) 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
RPM Version Numbers and Identifiers
The InfiniPath RPMs that are shipped have the InfiniPath release number and the build versions contained in the RPM name. The architecture is designated by
x86_64, noarch, or i386, and is dependent upon the distribution. For example:
infinipath-2.2-33597.832_rhel4_qlc.x86_64.rpm
In this RPM, 2.2 is the InfiniPath release, and 33597.832 are the build versions.