Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
Applies to SUSE Linux Enterprise High Availability Extension 15 SP2

3 Installing the High Availability Extension Edit source

If you are setting up a High Availability cluster with SUSE® Linux Enterprise High Availability Extension for the first time, the easiest way is to start with a basic two-node cluster. You can also use the two-node cluster to run some tests. Afterward, you can add more nodes by cloning existing cluster nodes with AutoYaST. The cloned nodes will have the same packages installed and the same system configuration as the original ones.

If you want to upgrade an existing cluster that runs an older version of SUSE Linux Enterprise High Availability Extension, refer to Chapter 5, Upgrading Your Cluster and Updating Software Packages.

3.1 Manual Installation Edit source

For the manual installation of the packages for High Availability Extension refer to Installation and Setup Quick Start. It leads you through the setup of a basic two-node cluster.

3.2 Mass Installation and Deployment with AutoYaST Edit source

After you have installed and set up a two-node cluster, you can extend the cluster by cloning existing nodes with AutoYaST and adding the clones to the cluster.

AutoYaST uses profiles that contains installation and configuration data. A profile tells AutoYaST what to install and how to configure the installed system to get a ready-to-use system in the end. This profile can then be used for mass deployment in different ways (for example, to clone existing cluster nodes).

For detailed instructions on how to use AutoYaST in various scenarios, see the AutoYaST Guide for SUSE Linux Enterprise Server 15 SP2.

Important
Important: Identical Hardware

Procedure 3.1, “Cloning a Cluster Node with AutoYaST” assumes you are rolling out SUSE Linux Enterprise High Availability Extension 15 SP2 to a set of machines with identical hardware configurations.

If you need to deploy cluster nodes on non-identical hardware, refer to the SUSE Linux Enterprise 15 SP2 Deployment Guide, chapter Automated Installation, section Rule-Based Autoinstallation.

Procedure 3.1: Cloning a Cluster Node with AutoYaST
  1. Make sure the node you want to clone is correctly installed and configured. For details, see the Installation and Setup Quick Start for SUSE Linux Enterprise High Availability Extension or Chapter 4, Using the YaST Cluster Module.

  2. Follow the description outlined in the SUSE Linux Enterprise 15 SP2 Deployment Guide for simple mass installation. This includes the following basic steps:

    1. Creating an AutoYaST profile. Use the AutoYaST GUI to create and modify a profile based on the existing system configuration. In AutoYaST, choose the High Availability module and click the Clone button. If needed, adjust the configuration in the other modules and save the resulting control file as XML.

      If you have configured DRBD, you can select and clone this module in the AutoYaST GUI, too.

    2. Determining the source of the AutoYaST profile and the parameter to pass to the installation routines for the other nodes.

    3. Determining the source of the SUSE Linux Enterprise Server and SUSE Linux Enterprise High Availability Extension installation data.

    4. Determining and setting up the boot scenario for autoinstallation.

    5. Passing the command line to the installation routines, either by adding the parameters manually or by creating an info file.

    6. Starting and monitoring the autoinstallation process.

After the clone has been successfully installed, execute the following steps to make the cloned node join the cluster:

Procedure 3.2: Bringing the Cloned Node Online
  1. Transfer the key configuration files from the already configured nodes to the cloned node with Csync2 as described in Section 4.5, “Transferring the Configuration to All Nodes”.

  2. To bring the node online, start the Pacemaker service on the cloned node as described in Section 4.8, “Bringing the Cluster Online Node by Node”.

The cloned node will now join the cluster because the /etc/corosync/corosync.conf file has been applied to the cloned node via Csync2. The CIB is automatically synchronized among the cluster nodes.

Print this page