|
|
|
|
NOTE: CentOS Enterprise Linux is built from the Red Hat Enterprise Linux source code. Other than logo and name changes CentOS Enterprise Linux is compatible with the equivalent Red Hat version. This document applies equally to both Red Hat and CentOS Enterprise Linux.
Chapter 3. Cluster Configuration
After installing and configuring the cluster hardware, the
cluster system software and cluster configuration software can be
installed.
Red Hat Cluster Suite consists of the following RPM
packages:
-
rgmanager — Manages cluster
services and resources
-
system-config-cluster — Contains
the Cluster Configuration Tool, used to
graphically configure the cluster and the display of the current
status of the nodes, resources, fencing agents, and cluster
services
-
ccsd — Contains the cluster
configuration services daemon (ccsd) and
associated files
-
magma — Contains an interface
library for cluster lock management
-
magma-plugins — Contains plugins
for the magma library
-
cman — Contains the Cluster
Manager (CMAN), which is used for managing cluster membership,
messaging, and notification
-
cman-kernel — Contains required
CMAN kernel modules
-
dlm — Contains distributed lock
management (DLM) library
-
dlm-kernel — Contains required
DLM kernel modules
-
fence — The cluster I/O fencing
system that allows cluster nodes to connect to a variety of network
power switches, fibre channel switches, and integrated power
management interfaces
-
gulm — Contains the GULM lock
management userspace tools and libraries (an alternative to using
CMAN and DLM).
-
iddev — Contains libraries used
to identify the file system (or volume manager) in which a device
is formatted
Also, you can optionally install Red Hat GFS on your Red Hat
Cluster Suite. Red Hat GFS consists of the following RPMs:
-
GFS — The Red Hat GFS module
-
GFS-kernel — The Red Hat GFS
kernel module
-
gnbd — The GFS Network Block
Device module
-
gnbd-kernel — Kernel module for
the GFS Network Block Device
-
lvm2-cluster — Cluster
extensions for the logical volume manager
-
GFS-kernheaders — GFS kernel
header files
-
gnbd-kernheaders — gnbd kernel header files
|
Tip |
|
You can access the Red Hat Cluster Suite and Red Hat GFS
products by using Red Hat Network to subscribe to and access the
channels containing the Red Hat Cluster Suite and Red Hat GFS
packages. From the Red Hat Network channel, you can manage
entitlements for your cluster nodes and upgrade packages for each
node within the Red Hat Network Web-based interface. For more
information on using Red Hat Network, visit the following URL:
|
You can install Red Hat Cluster Suite and Red Hat GFS RPMs using
either of the following methods:
For automatic RPM installation, refer to Section 3.1.1 Automatic RPM
Installation. For custom RPM installation, refer to
Section 3.1.2 Custom
RPM Installation.
Automatic RPM installation consists of running the up2date utility at each node for the Red Hat Cluster
Suite and Red Hat GFS products.
|
Note |
|
If you are installing the GFS RPMs, you must run up2date for Red Hat Cluster Suite before running it
for Red Hat GFS.
|
To automatically install RPMs, do the following at each
node:
-
Log on as the root user.
-
Run up2date --installall --channel
Label for Red Hat Cluster
Suite. The following example shows running the command for i386
RPMs:
# up2date --installall --channel rhel-i386-as-4-cluster
|
-
(Optional) If you are installing Red Hat GFS, run up2date --installall --channel Label for Red Hat GFS. The following
example shows running the command for i386 RPMs:
# up2date --installall --channel rhel-i386-as-4-gfs-6.1
|
Custom RPM installation consists of the following steps:
-
Determine which RPMs to install. For information on determining
which RPMs to install, refer to Section 3.1.2.1
Determining RPMs To Install.
-
Install the RPMs using the rpm utility.
For information about installing the RPMs using the rpm utility, refer to Section 3.1.2.2 Installing
Packages with the rpm Utility.
|
Note |
|
If you are installing the GFS RPMs, you must install Red Hat
Cluster Suite before Red Hat GFS.
|
Determining which RPMs to install is based on the following
criteria:
-
The lock manager Red Hat Cluster Suite is using — either
DLM or GULM
-
The Red Hat Cluster Suite and Red Hat GFS functions you are
using (besides the standard functions)
-
Whether to include development libraries
-
The type of kernel (or kernels) is installed
Use the following tables for determining which RPMs to
install:
The tables contain the following information to assist you in
determining which packages to install:
-
RPMs — The names of the RPMs (excluding revision
numbers)
-
Inclusion — The tables provide the following information
about whether an RPM should be included in the installation:
-
Req: Required RPM — You must
install the RPM.
-
Opt: Optional RPM — Refer to the "Purpose" for more
information about determining whether to include the RPM.
-
Dev: Development RPM — Used for development purposes.
Refer to the "Purpose" for more information about determining
whether to include the RPM.
-
Purpose — Provides a concise description of the RPM
purpose. Assists in determining which RPMs to include other than
the required RPMs.
To determine which RPMs to include in the installation, perform
the following steps:
-
Determine whether you are installing Red Hat Cluster Suite with
DLM or Red Hat Cluster Suite with GULM.
-
If you are installing Red Hat Cluster Suite with DLM, refer to
Table 3-1 to identify
which RPMs are required, optional, and for development.
-
If you are installing Red Hat Cluster Suite with GULM, refer to
Table 3-2 to
identify which RPMs are required, optional, and for
development.
-
If you are installing Red Hat GFS, refer to Table 3-3 to identify which RPMs
are required, optional, and for development.
-
With the information gathered in the previous steps, proceed to
install the RPMs using the procedures in Section 3.1.2.2 Installing
Packages with the rpm Utility.
RPMs |
Inclusion |
Depends on Kernel Type? |
Purpose |
ccs-ver-rel.arch |
Req |
No |
The Cluster Configuration System |
cman-ver-rel.arch |
Req |
No |
The Cluster Manager |
cman-kernel-ver-rel.arch |
cman-kernel-hugemem-ver-rel.arch |
cman-kernel-smp-ver-rel.arch |
Note: The types of RPMs available vary
according to RHN channel. |
|
Req |
Yes |
The Cluster Manager kernel modules |
dlm-ver-rel.arch |
Req |
No |
The Distributed Lock Manager |
dlm-kernel-ver-rel.arch |
dlm-kernel-hugemem-ver-rel.arch |
dlm-kernel-smp-ver-rel.arch |
Note: The types of RPMs available vary
according to RHN channel. |
|
Req |
Yes |
The Distributed Lock Manager kernel modules |
fence-ver-rel.arch |
Req |
No |
The cluster I/O fencing system |
iddev-ver-rel.arch |
Req |
No |
A library that identifies device contents |
magma-ver-rel.arch |
Req |
No |
A cluster/lock manager API abstraction library |
magma-plugins-ver-rel.arch |
Req |
No |
Cluster manager plugins for magma |
gulm-ver-rel.arch |
Note: The gulm
module is required with DLM because the magma-plugins module has a dependency on the
gulm RPM. |
|
Req |
No |
The Grand Unified Lock Manager (GULM, available for this
release and earlier versions of Red Hat GFS) |
perl-Net-Telnet-ver-rel.arch |
Req |
No |
Net-Telnet Perl module |
rgmanager-ver-rel.arch |
Opt |
No |
Open source HA resource group failover |
system-config-cluster-ver-rel.arch |
Req |
No |
GUI to manage cluster configuration |
ipvsadm-ver-rel.arch |
Opt |
No |
Utility to administer the Linux Virtual Server |
piranha-ver-rel.arch |
Opt |
No |
Cluster administration tools |
ccs-devel-ver-rel.arch |
Dev |
No |
CCS static library |
cman-kernheaders-ver-rel.arch |
Dev |
No |
cman kernel header files |
dlm-devel-ver-rel.arch |
Dev |
No |
The Distributed Lock Manager user-space libraries |
dlm-kernheaders-ver-rel.arch |
Dev |
No |
dlm kernel header files |
iddev-devel-ver-rel.arch |
Dev |
No |
iddev development libraries |
magma-devel-ver-rel.arch |
Dev |
No |
A cluster/lock manager API abstraction library |
Table 3-1. RPM Selection Criteria: Red Hat Cluster Suite with
DLM
RPMs |
Inclusion |
Depends on Kernel Type? |
Purpose |
ccs-ver-rel.arch |
Req |
No |
The Cluster Configuration System |
fence-ver-rel.arch |
Req |
No |
The cluster I/O fencing system |
gulm-ver-rel.arch |
Req |
No |
The Grand Unified Lock Manager (GULM, available for this
release and earlier versions of Red Hat GFS) |
iddev-ver-rel.arch |
Req |
No |
A library that identifies device contents |
magma-ver-rel.arch |
Req |
No |
A cluster/lock manager API abstraction library |
magma-plugins-ver-rel.arch |
Req |
No |
Cluster manager plugins for magma |
perl-Net-Telnet-ver-rel.arch |
Req |
No |
Net-Telnet Perl module |
system-config-cluster-ver-rel.arch |
Req |
No |
GUI to manage cluster configuration |
ipvsadm-ver-rel.arch |
Opt |
No |
Utility to administer the Linux Virtual Server |
piranha-ver-rel.arch |
Opt |
No |
Cluster administration tools |
ccs-devel-ver-rel.arch |
Dev |
No |
CCS static library |
gulm-devel-ver-rel.arch |
Dev |
No |
gulm libraries |
iddev-devel-ver-rel.arch |
Dev |
No |
iddev development libraries |
magma-devel-ver-rel.arch |
Dev |
No |
A cluster/lock manager API abstraction library |
Table 3-2. RPM Selection Criteria: Red Hat Cluster Suite with
GULM
RPMs |
Inclusion |
Depends on Kernel Type? |
Purpose |
GFS-ver-rel.arch |
Req |
No |
The Red Hat GFS module |
GFS-kernel-ver-rel.arch |
GFS-kernel-hugemem-ver-rel.arch |
GFS-kernel-smp-ver-rel.arch |
Note: The types of RPMs available vary
according to RHN channel. |
|
Req |
Yes |
The Red Hat GFS kernel modules |
gnbd-ver-rel.arch |
Opt |
No |
The GFS Network Block Device |
gnbd-kernel-ver-rel.arch |
gnbd-kernel-hugemem-ver-rel.arch |
gnbd-kernel-smp-ver-rel.arch |
Note: The types of RPMs available vary
according to RHN channel. |
|
Opt |
Yes |
Kernel module for GFS Network Block Device |
lvm2-cluster-ver-rel.arch |
Req |
No |
Cluster extensions for the logical volume manager |
GFS-kernheaders-ver-rel.arch |
Dev |
No |
GFS kernel header files |
gnbd-kernheaders-ver-rel.arch |
Dev |
No |
gnbd kernel header files |
Table 3-3. RPM Selection Criteria: Red Hat GFS
You can use the rpm utility to install
RPMs from CDs created with RHN ISOs. The procedure consists of
copying RPMs to a local computer, removing the RPMs that are not
needed for the installation, copying the RPMs to the cluster nodes,
and installing them.
To install the RPMs, follow these instructions:
-
At a local computer (one that is not part of the cluster) make a
temporary directory to contain the RPMs. For example:
-
Insert the Red Hat Cluster Suite CD into the CD-ROM drive.
|
Note |
|
If a Question dialog box is displayed
that asks if you want to run autorun,
click No.
|
-
Copy all the RPM files from the CD (located in /media/cdrom/RedHat/RPMS/) to the temporary
directory created earlier. For example:
$ cp /media/cdrom/RedHat/RPMS/*.rpm /tmp/RPMS/
|
|
Note |
|
If your local computer is running a version of Red Hat
Enterprise Linux that is earlier than Red Hat Enterprise Linux 4,
the path to the RPMs on the CD may be different. For example, on
Red Hat Enterprise Linux 3, the path is /mnt/cdrom/RedHat/RPMS/.
|
-
Eject the CD from the CD-ROM drive.
-
(Optional) If you are installing Red Hat GFS, insert a Red Hat
GFS CD into the CD-ROM drive. If you are not installing Red Hat
GFS, proceed to step 8.
|
Note |
|
If a Question dialog box is displayed
that asks if you want to run autorun,
click No.
|
-
Copy all the RPM files from the CD (located in /media/cdrom/RedHat/RPMS/) to the temporary
directory created earlier. For example:
$ cp /media/cdrom/RedHat/RPMS/*.rpm /tmp/RPMS/
|
|
Note |
|
If your local computer is running a version of Red Hat
Enterprise Linux that is earlier than Red Hat Enterprise Linux 4,
the path to the RPMs on the CD may be different. For example, on
Red Hat Enterprise Linux 3, the path is /mnt/cdrom/RedHat/RPMS/.
|
-
Eject the CD from the CD-ROM drive.
-
Change to the temporary directory containing the copied RPM
files. For example:
-
Remove the "-kernel" RPMs for kernels that are not installed in
the cluster node, and any other RPMs that are not being installed
(for example, optional or development RPMS). The following example
removes SMP and hugemem "-kernel" RPM files:
$ rm *-kernel-smp* *-kernel-hugemem*
|
For information about selecting the RPMs to install, refer to
Section 3.1.2.1
Determining RPMs To Install.
-
Log in to each cluster node as the root user and make a
directory to contain the RPMs. For example:
-
Copy the RPMs from the temporary directory in the local computer
to directories in the cluster nodes using the scp command. For example, to copy the RPMs to node
rhcs-node-01, run the following command at the local computer:
$ scp /tmp/RPMS/*.rpm root@rhcs-node-01:/tmp/node-RPMS/
|
-
At each node (logged in as root), change to the temporary
directory created earlier (/tmp/node-RPMS) and install the RPMs by running the
rpm utility as follows:
# cd /tmp/node-RPMS/
# rpm -Uvh *
|
|
|
|