QLogic 7104-7M-CABLE ユーザーズマニュアル
D–Package Descriptions
Different Nodes May Use Different RPMs
Different Nodes May Use Different RPMs
D-2
IB0056101-00 H
S
Once the Installer tool has begun the installation, for some packages, the
underlying RPM names are displayed on the screen.
underlying RPM names are displayed on the screen.
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:
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.
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.
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.
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
software is required on all nodes. See
, or
for
information on installation of software RPMs on specific types of nodes.
InfiniPath RPM Version Numbers and Identifiers
The InfiniPath RPMs that are shipped have the InfiniPath release number, build
identifiers, and distribution contained in the RPM name. The architecture is
designated by x86_64, noarch, or i386, and is dependent upon the distribution.
identifiers, and distribution contained in the RPM name. The architecture is
designated by x86_64, noarch, or i386, and is dependent upon the distribution.
For example:
infinipath-<release>-<build_identifier>_<distro>_qlc.x86_64.rpm
Note that _qlc is always added after the distribution identifier.
In the InfiniPath tables in this appendix, the release and build identifiers are
contained in xxx. The distribution identifier plus _qlc is contained in yyy. Using
In the InfiniPath tables in this appendix, the release and build identifiers are
contained in xxx. The distribution identifier plus _qlc is contained in yyy. Using
this convention, the previous RPM would be listed as:
infinipath-xxx_yyy.x86_64.rpm
OpenFabrics RPM Names
Non-InfiniPath components have their own version numbering, which can vary
depending on the source of the RPM. For example:
depending on the source of the RPM. For example:
mvapich_gcc-1.1.0-3143.x86_64.rpm
1_1_0 is the 1.1.0 build for mvapich. In the following tables, the version number
is replaced by xxx.