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

E Upgrading Your Cluster and Updating Software Packages

This chapter covers two different scenarios: upgrading a cluster to another version of SUSE® Linux Enterprise High Availability Extension (either a major release or a service pack) as opposed to updating individual packages on cluster nodes.

E.1 Terminology

In the following, find definitions of the most important terms used in this chapter:

Major Release, General Availability (GA) Version

The Major Release of SUSE Linux Enterprise (or any software product) is a new version which brings new features and tools, decommissions previously deprecated components and comes with backward incompatible changes.

Service Pack (SP)

Combines several patches into a form which is easy to install or deploy. Service packs are numbered and usually contain security fixes, updates, upgrades, or enhancements of programs.

Update

Installation of a newer minor version of a package.

Upgrade

Installation of a newer major version of a package or distribution, which brings new features.

E.2 Upgrading your Cluster to the Latest Product Version

Which upgrade path is supported and how to perform the upgrade depends on the current product version your cluster is running on and on the target version you want to migrate to. For general information on this, see the SUSE Linux Enterprise Server 11 Deployment Guide, chapter Updating SUSE Linux Enterprise. It is available at http://documentation.suse.com/.

Important
Important: Required Preparations Before Upgrading
  • Ensure that your system backup is up to date and restorable.

  • Test the upgrade procedure on a staging instance of your cluster setup first, before performing it in a production environment.

    This gives you an estimation of the time frame required for the maintenance window. It also helps to detect and solve any unexpected problems that might arise.

E.2.1 Upgrading from SLES 10 to SLE HA 11

Important
Important: Taking Cluster Offline is Required

For migrating from SUSE Linux Enterprise Server 10 to SUSE Linux Enterprise Server 11 (any service pack), all cluster nodes must be offline and the cluster must be migrated as a whole—mixed clusters running on SUSE Linux Enterprise Server 10/SUSE Linux Enterprise Server 11 are not supported.

For convenience, SUSE Linux Enterprise High Availability Extension includes a hb2openais.sh script with which to convert your data while moving from the Heartbeat to the OpenAIS cluster stack. The script parses the configuration stored in /etc/ha.d/ha.cf and generates a new configuration file for the OpenAIS cluster stack. Furthermore, it adjusts the CIB to match the OpenAIS conventions, converts the OCFS2 file system and replaces EVMS with cLVM. Any EVMS2 containers are converted to cLVM2 volumes. For volume groups referenced in existing resources in the CIB, new LVM resources are created.

To successfully migrate your cluster from SUSE Linux Enterprise Server 10 SP4 to SUSE Linux Enterprise Server 11, you need to execute the following steps:

After the conversion has been successfully completed, you can bring the upgraded cluster online again.

Note
Note: Reverting after Upgrade

After the upgrade process to SUSE Linux Enterprise Server 11, reverting back to SUSE Linux Enterprise Server 10 is not supported.

E.2.1.1 Preparation and Backup

Before upgrading your cluster to the next product version and converting the data accordingly, you need to prepare your current cluster.

Procedure E.1: Preparing your SUSE Linux Enterprise Server 10 SP4 Cluster
  1. Log in to the cluster.

  2. Review the Heartbeat configuration file /etc/ha.d/ha.cf and check that all communication media support multicasting.

  3. Make sure the following files are equal on all nodes: /etc/ha.d/ha.cf and /var/lib/heartbeat/crm/cib.xml.

  4. Take all nodes offline by executing rcheartbeat stop on each node.

  5. In addition to the general system backup recommended before updating to the latest version, back up the following files, as you need them for running the conversion script after the upgrade to SUSE Linux Enterprise Server 11:

    • /var/lib/heartbeat/crm/cib.xml

    • /var/lib/heartbeat/hostcache

    • /etc/ha.d/ha.cf

    • /etc/logd.cf

  6. If you have EVMS2 resources, convert non-LVM EVMS2 volumes to compatibility volumes on SUSE Linux Enterprise Server 10. During the conversion process (see Section E.2.1.3, “Data Conversion”), these are then turned into LVM2 volume groups. After conversion, make sure to mark each volume group as a member of the High Availability cluster with vgchange -c y.

E.2.1.2 Upgrade/Installation

After preparing the cluster and backing up the files, do a fresh installation of SUSE Linux Enterprise 11 on your cluster nodes.

Procedure E.2: Upgrading to SUSE Linux Enterprise 11
  1. Freshly install SUSE Linux Enterprise Server 11 on all cluster nodes.

  2. On all cluster nodes, install SUSE Linux Enterprise High Availability Extension 11 as add-on on top of SUSE Linux Enterprise Server. For detailed information, see Section 3.3, “Installation as Add-on”.

E.2.1.3 Data Conversion

After having installed SUSE Linux Enterprise Server 11 and the High Availability Extension, you can start with the data conversion. The conversion script shipped with the High Availability Extension has been set up with care, but it cannot handle all set-ups in fully automatic mode. It alerts you of the changes it makes, but needs interaction and decisions from your side. You need to know your cluster in detail—it is up to you to verify that the changes are meaningful. The conversion script is located in /usr/lib/heartbeat (or in /usr/lib64/heartbeat, if you are using a 64-bit system).

Note
Note: Executing Test Runs

To make yourself familiar with the conversion process, we highly recommend that you test the conversion first (without making any changes). You can use the same test directory to do repeated test runs, but you only need to copy the files once.

Procedure E.3: Testing the Conversion
  1. On one of the nodes, create a test directory and copy the backup files to the test directory:

    $ mkdir /tmp/hb2openais-testdir
    $ cp /etc/ha.d/ha.cf /tmp/hb2openais-testdir
    $ cp /var/lib/heartbeat/hostcache /tmp/hb2openais-testdir
    $ cp /etc/logd.cf /tmp/hb2openais-testdir
    $ sudo cp /var/lib/heartbeat/crm/cib.xml /tmp/hb2openais-testdir
  2. Start the test run with

    $ /usr/lib/heartbeat/hb2openais.sh -T /tmp/hb2openais-testdir -U

    or with the following command, if you are using a 64-bit system:

    $ /usr/lib64/heartbeat/hb2openais.sh -T /tmp/hb2openais-testdir -U
  3. Read and verify the resulting openais.conf and cib-out.xml files:

    $ cd  /tmp/hb2openais-testdir 
    $ less openais.conf 
    $ crm_verify -V -x cib-out.xml

For detailed information about the conversion stages, refer to /usr/share/doc/packages/pacemaker/README.hb2openais in your installed High Availability Extension.

Procedure E.4: Converting the Data

After doing a test run and checking the output, you can now start with the data conversion. You only need to run the conversion on one node. The main cluster configuration (the CIB) is automatically replicated to the other nodes. All other files that need to be replicated are automatically copied by the conversion script.

  1. Make sure that sshd is running on all nodes with access allowed for root in order for the conversion script to successfully copy the files to the other cluster nodes.

  2. Make sure that all ocfs2 file systems are unmounted.

  3. The High Availability Extension ships with a default OpenAIS configuration file. If you want to prevent the default configuration from being overwritten during the following steps, make a copy of the /etc/ais/openais.conf configuration file.

  4. Start the conversion script as root. If using sudo, specify the privileged user using the -u option:

    $ /usr/lib/heartbeat/hb2openais.sh -u root

    Based on the configuration stored in /etc/ha.d/ha.cf, the script will generate a new configuration file for the OpenAIS cluster stack, /etc/ais/openais.conf. It will also analyze the CIB configuration and let you know if your cluster configuration requires changes, due to the change from Heartbeat to OpenAIS. All file processing is done on the node where conversion runs and replicated to the other nodes.

  5. Follow the instructions on the screen.

After the conversion has been finished successfully, start the new cluster stack as described in Section 3.5.7, “Bringing the Cluster Online”.

After the upgrade process, reverting back to SUSE Linux Enterprise Server 10 is not supported.

E.2.1.4 For More Information

For more details about the conversion script and the stages of the conversion, refer to /usr/share/doc/packages/pacemaker/README.hb2openais in your installed High Availability Extension.

E.2.2 Upgrading from SLE HA 11 to SLE HA 11 SP1

Note
Note: Rolling Upgrade Between Service Pack Versions

To successfully migrate an existing cluster from one service pack version to the next one, you can do a rolling upgrade, meaning upgrading one node after the other.

As the main cluster configuration file has changed from /etc/ais/openais.conf to /etc/corosync/corosync.conf with SUSE Linux Enterprise High Availability Extension 11 SP1, a script takes care of the necessary conversions. They are executed automatically when the openais package is updated.

Procedure E.5: Performing a Rolling Upgrade
Warning
Warning: Active Cluster Stack During Update

To update any software packages on a node that is part of a running cluster, stop the cluster stack on that node before starting the software update. In some cases (see Conditions for Stopping the Cluster Stack, you can alternatively put the cluster into maintenance mode (which is available since SUSE Linux Enterprise High Availability Extension 11 SP4).

If the cluster resource manager on a node is active during the software update, this can lead to unpredictable results like fencing of active nodes.

  1. Log in as root on the node that you want to upgrade and stop OpenAIS:

    rcopenais stop
  2. Check that your system backup is up-to-date and restorable.

  3. Perform an upgrade from SUSE Linux Enterprise Server 11 to SUSE Linux Enterprise Server 11 SP1 and from SUSE Linux Enterprise High Availability Extension 11 to SUSE Linux Enterprise High Availability Extension 11 SP1. For information on how to upgrade your product, refer to the SUSE Linux Enterprise Server 11 SP1 Deployment Guide, chapter Updating SUSE Linux Enterprise.

  4. Restart OpenAIS/Corosync on the upgraded node to make the node rejoin the cluster:

    rcopenais start
  5. Take the next node offline and repeat the procedure for that node.

E.2.3 Upgrading from SLE HA 11 SP1 to SLE HA 11 SP2

Migrating an existing cluster from SUSE Linux Enterprise High Availability Extension 11 SP1 to 11 SP2 is done via a rolling upgrade, similar to the upgrade procedure from version 11 to 11 SP1.

Proceed as described in Procedure E.5, “Performing a Rolling Upgrade” with the following two deviations:

  • In Step 3, upgrade from SUSE Linux Enterprise Server 11  SP1 to SUSE Linux Enterprise Server 11 SP2 and from SUSE Linux Enterprise High Availability Extension 11 SP1 to SUSE Linux Enterprise High Availability Extension 11 SP2.

    As Xen Hypervisor is discontinued for 32-bit architectures, you might need to solve dependencies for the package drbd-xen manually. Note that cross-platform clusters are not supported.

  • Because of the Kernel update shipped with SP2, reboot the node between Step 3 and Step 4.

Important
Important: Time Limit for Rolling Upgrade

The new features shipped with SUSE Linux Enterprise High Availability Extension 11 SP2 will only be available after all cluster nodes have been upgraded to the latest product version. Mixed SP1/SP2 clusters are only supported for a short time frame during the rolling upgrade. Complete the rolling upgrade within one week.

E.2.4 Upgrading from SLE HA 11 SP2 to SLE HA 11 SP3

Migrating an existing cluster from SUSE Linux Enterprise High Availability Extension 11 SP2 to 11 SP3 is done via a rolling upgrade, similar to the upgrade procedure from version 11 to 11 SP1.

Proceed as described in Procedure E.5, “Performing a Rolling Upgrade” with the following deviation: In Step 3, upgrade from SUSE Linux Enterprise Server 11  SP2 to SUSE Linux Enterprise Server 11 SP3 and from SUSE Linux Enterprise High Availability Extension 11 SP2 to SUSE Linux Enterprise High Availability Extension 11 SP3.

Important
Important: Time Limit for Rolling Upgrade

The new features shipped with SUSE Linux Enterprise High Availability Extension 11 SP3 will only be available after all cluster nodes have been upgraded to the latest product version. Mixed SP2/SP3 clusters are only supported for a short time frame during the rolling upgrade. Complete the rolling upgrade within one week.

E.2.5 Upgrading from SLE HA 11 SP3 to SLE HA 11 SP4

Migrating an existing cluster from SUSE Linux Enterprise High Availability Extension 11 SP3 to 11 SP4 is done via a rolling upgrade, similar to the upgrade procedure from version 11 to 11 SP1.

Proceed as described in Procedure E.5, “Performing a Rolling Upgrade” with the following deviation: In Step 3, upgrade from SUSE Linux Enterprise Server 11  SP3 to SUSE Linux Enterprise Server 11 SP4 and from SUSE Linux Enterprise High Availability Extension 11 SP3 to SUSE Linux Enterprise High Availability Extension 11 SP4.

Note
Note: Upgrading the CIB Syntax Version

Tags (for grouping resources) and some ACL features only work with the CIB syntax version pacemaker-2.0 or higher. (To check your version, run cibadmin -Q |grep validate-with). If you have upgraded from SUSE Linux Enterprise High Availability Extension 11 SP3, your CIB version will not be upgraded by default. To manually upgrade to the latest CIB version use one of the following commands:

root # cibadmin --upgrade --force

or

root # crm configure upgrade force
Important
Important: Time Limit for Rolling Upgrade

The new features shipped with SUSE Linux Enterprise High Availability Extension 11 SP4 will only be available after all cluster nodes have been upgraded to the latest product version. Mixed SP3/SP4 clusters are only supported for a short time frame during the rolling upgrade. Complete the rolling upgrade within one week.

E.3 Updating Software Packages on Cluster Nodes

Warning
Warning: Active Cluster Stack During Update

To update any software packages on a node that is part of a running cluster, stop the cluster stack on that node before starting the software update. In some cases (see Conditions for Stopping the Cluster Stack, you can alternatively put the cluster into maintenance mode (which is available since SUSE Linux Enterprise High Availability Extension 11 SP4).

If the cluster resource manager on a node is active during the software update, this can lead to unpredictable results like fencing of active nodes.

Before installing any package updates on a node, check the following:

Conditions for Stopping the Cluster Stack
  • Does the update affect any packages belonging to SUSE Linux Enterprise High Availability Extension or the Geo Clustering for SUSE Linux Enterprise High Availability Extension add-on? If yes: Stop the cluster stack on the node before starting the software update.

    root # rcopenais stop
  • Does the package update require a reboot? If yes: Stop the cluster stack on the node before starting the software update:

    root # rcopenais stop

If none of the situations above apply, you do not need to stop the cluster stack. In that case, put the cluster into maintenance mode before starting the software update:

root # crm configure property maintenance-mode=true

For more details on maintenance mode, see Section 4.7, “Maintenance Mode”.

After the update has been successfully installed, remove the cluster maintenance mode:

root # crm configure property maintenance-mode=false

or restart the cluster stack on the respective node with:

root # rcopenais start

E.4 For More Information

For detailed information about any changes and new features of the product you are upgrading to, refer to its release notes. They are available from https://www.suse.com/releasenotes/.

Print this page