Installation guide

Chapter 6. Configuration and Administration Tools
The cluster configuration file, /etc/cl uster/cl uster. co nf specifies the High Availability Add-On
configuration.The configuration file is an XML file that describes the following cluster characteristics:
Cluster name — Specifies the cluster name, cluster configuration file revision level, and basic
fence timing properties used when a node joins a cluster or is fenced from the cluster.
Cluster — Specifies each node of the cluster, specifying node name, node ID, number of quorum
votes, and fencing method for that node.
Fence Device — Specifies fence devices in the cluster. Parameters vary according to the type of
fence device. For example for a power controller used as a fence device, the cluster configuration
defines the name of the power controller, its IP address, login, and password.
Managed Resources — Specifies resources required to create cluster services. Managed
resources includes the definition of failover domains, resources (for example an IP address), and
services. Together the managed resources define cluster services and failover behavior of the
cluster services.
The cluster configuration is automatically validated according to the cluster schema at
/usr/share/cl uster/cl uster.rng during startup time and when a configuration is reloaded.
Also, you can validate a cluster configuration any time by using the ccs_confi g _val i d ate
command.
An annotated schema is available for viewing at /usr/share/d o c/cman-
X. Y . ZZ/cl uster_co nf. html (for example /usr/share/do c/cman-
3. 0 . 12/cl uster_co nf.html ).
Configuration validation checks for the following basic errors:
XML validity — Checks that the configuration file is a valid XML file.
Configuration options — Checks to make sure that options (XML elements and attributes) are
valid.
Option values — Checks that the options contain valid data (limited).
6.1. Clust er Administ rat ion T ools
Managing Red Hat High Availability Add-On software consists of using configuration tools to specify
the relationship among the cluster components. The following cluster configuration tools are
available with Red Hat High Availability Add-On:
Co n g a — This is a comprehensive user interface for installing, configuring, and managing Red
Hat High Availability Add-On. Refer to Configuring and Managing the High Availability Add-On for
information about configuring and managing High Availability Add-On with Co n g a.
Luci — This is the application server that provides the user interface for Conga. It allows users
to manage cluster services and provides access to help and online documentation when
needed.
Ricci — This is a service daemon that manages distribution of the cluster configuration. Users
pass configuration details using the Luci interface, and the configuration is loaded in to
corosync for distribution to cluster nodes.
As of the Red Hat Enterprise Linux 6.1 release and later, the Red Hat High Availability Add-On
Red Hat Ent erprise Linux 6 High Availabilit y Ad d- O n O verview
28