Installation guide
36 Chapter 1. Red Hat Cluster Suite Overview
• Fence Devices — Displays fence devices. Fence devices are represented as subordinate
elements under Fence Devices. Using configuration buttons at the bottom of the right
frame (below Properties), you can add fence devices, delete fence devices, and edit
fence-device properties. Fence devices must be defined before you can configure fencing
(with the Manage Fencing For This Node button) for each node.
• Managed Resources — Displays failover domains, resources, and services.
• Failover Domains — For configuring one or more subsets of cluster nodes used to
run a high-availability service in the event of a node failure. Failover domains are rep-
resented as subordinate elements under Failover Domains. Using configuration but-
tons at the bottom of the right frame (below Properties), you can create failover do-
mains (when Failover Domains is selected) or edit failover domain properties (when
a failover domain is selected).
• Resources — For configuring shared resources to be used by high-availability ser-
vices. Shared resources consist of file systems, IP addresses, NFS mounts and ex-
ports, and user-created scripts that are available to any high-availability service in the
cluster. Resources are represented as subordinate elements under Resources. Using
configuration buttons at the bottom of the right frame (below Properties), you can
create resources (when Resources is selected) or edit resource properties (when a
resource is selected).
Note
The Cluster Configuration Tool provides the capability to configure private re-
sources, also. A private resource is a resource that is configured for use with only
one service. You can configure a private resource within a Service component in
the GUI.
• Services — For creating and configuring high-availability services. A service is con-
figured by assigning resources (shared or private), assigning a failover domain, and
defining a recovery policy for the service. Services are represented as subordinate el-
ements under Services. Using configuration buttons at the bottom of the right frame
(below Properties), you can create services (when Services is selected) or edit service
properties (when a service is selected).
Figure 1-25 shows an example of the hierarchical relationship among cluster nodes, high-
availability services, and resources. The cluster nodes are connected to one or more fencing
devices. Nodes can be grouped into a failover domain for a cluster service. The services
comprise resources such as NFS exports, IP addresses, and shared GFS partitions.