Show Table of Contents
Chapter 4. Configuring Red Hat High Availability Add-On With Conga
This chapter describes how to configure Red Hat High Availability Add-On software using Conga. For information on using Conga to manage a running cluster, see Chapter 5, Managing Red Hat High Availability Add-On With Conga.
Note
Conga is a graphical user interface that you can use to administer the Red Hat High Availability Add-On. Note, however, that in order to use this interface effectively you need to have a good and clear understanding of the underlying concepts. Learning about cluster configuration by exploring the available features in the user interface is not recommended, as it may result in a system that is not robust enough to keep all services running when components fail.
This chapter consists of the following sections:
4.1. Configuration Tasks
Configuring Red Hat High Availability Add-On software with Conga consists of the following steps:
- Configuring and running the Conga configuration user interface — the luci server. Refer to Section 4.2, “Starting luci”.
- Creating a cluster. Refer to Section 4.4, “Creating a Cluster”.
- Configuring global cluster properties. Refer to Section 4.5, “Global Cluster Properties”.
- Configuring fence devices. Refer to Section 4.6, “Configuring Fence Devices”.
- Configuring fencing for cluster members. Refer to Section 4.7, “Configuring Fencing for Cluster Members”.
- Creating failover domains. Refer to Section 4.8, “Configuring a Failover Domain”.
- Creating resources. Refer to Section 4.9, “Configuring Global Cluster Resources”.
- Creating cluster services. Refer to Section 4.10, “Adding a Cluster Service to the Cluster”.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.