Upgrading Your Cluster and Updating Software Packages | Administration Guide | SUSE Linux Enterprise High Availability Extension 12

SUSE Linux Enterprise High Availability Extension Documentation › Administration Guide › Appendix › Upgrading Your Cluster and Updating Software Packages

ContentsContents

Administration Guide

Navigation←→

Applies to SUSE Linux Enterprise High Availability Extension 12

D Upgrading Your Cluster and Updating Software Packages

D.1 Terminology
D.2 Upgrading your Cluster to the Latest Product Version
D.3 Updating Software Packages on Cluster Nodes
D.4 For More Information

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.

D.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 backwards 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.

D.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 12 Deployment Guide, chapter Updating SUSE Linux Enterprise. It is available at http://www.suse.com/documentation/.

D.2.1 Upgrading from SLE HA 11 SP3 to SLE HA 12 #

In order to successfully upgrade to SUSE Linux Enterprise High Availability Extension 12, your cluster needs to run the latest versions of SUSE Linux Enterprise Server and SUSE Linux Enterprise High Availability Extension (11 SP3). If your cluster is still based on an older product version, upgrade it to SUSE Linux Enterprise Server and SUSE Linux Enterprise High Availability Extension 11 SP3 first. Find information on this in the High Availability Guide for SUSE Linux Enterprise High Availability Extension 11, chapter Upgrading Your Cluster to the Latest Product Version. It is available at http://www.suse.com/documentation/.

Due to major changes in various components of the High Availability Extension 12 (for example, /etc/corosync/corosync.conf, disk formats of OCFS2), performing a rolling upgrade is not supported for this scenario. All cluster nodes must be offline and the cluster needs to be migrated as a whole as described in Procedure D.1, “Upgrading the Cluster to SLE HA 12”. Mixed clusters running on SUSE Linux Enterprise High Availability Extension 11/SUSE Linux Enterprise High Availability Extension 12 are not supported.

Procedure D.1: Upgrading the Cluster to SLE HA 12 #

Important: Required Preparations Before Upgrading

Ensure that your system back-up 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.

Execute the following steps for each cluster node:

Log in to each cluster node and stop the cluster stack with:
```
root #  rcopenais stop
```
For each cluster node, perform an upgrade from SUSE Linux Enterprise Server 11 SP3 to SUSE Linux Enterprise Server 12 and from SUSE Linux Enterprise High Availability Extension 11 SP3 to SUSE Linux Enterprise High Availability Extension 12. If you want to make use of GEO clustering, install the respective add-on as described in the GEO Clustering for SUSE Linux Enterprise High Availability Extension Quick Start. For information on how to upgrade your product, see the SUSE Linux Enterprise Server 12 Deployment Guide, chapter Updating SUSE Linux Enterprise. It is available at http://www.suse.com/documentation/.
After the upgrade process has finished, reboot each node with version 12 of SUSE Linux Enterprise Server and SUSE Linux Enterprise High Availability Extension.
If you use OCFS2 in your cluster setup, update the on-device structure by executing the following command:
```
root #  tunefs.ocfs2 --update-cluster-stack PATH_TO_DEVICE
```
It adds additional parameters to the disk which are needed for the updated OCFS2 version that is shipped with SUSE Linux Enterprise High Availability Extension 12.
To update /etc/corosync/corosync.conf for Corosync version 2:
1. Log in to one node and start the YaST cluster module.
2. Switch to the Communication Channels category and enter values for the following new parameters: Cluster Name and Expected Votes. For details, see Procedure 3.5, “Defining the First Communication Channel”.
  If YaST should detect any other options that are invalid or missing according to Corosync version 2, it will prompt you to change them.
3. Confirm your changes in YaST to update /etc/corosync/corosync.conf.
4. If Csync2 is configured for your cluster, use the following command to push the updated Corosync configuration to the other cluster nodes:
```
root # csync2 -xv
```
  For details on Csync2, see Section 3.5.4, “Transferring the Configuration to All Nodes”.
  Alternatively, synchronize the updated Corosync configuration by manually copying /etc/corosync/corosync.conf to all cluster nodes.
Log in to each node and start the cluster stack with:
```
root #  systemctl start pacemaker.service
```
Check the cluster status with crm status or with Hawk.

If you have an existing GEO cluster setup and want to upgrade it to run with High Availability Extension 12 and GEO Clustering for SUSE Linux Enterprise High Availability Extension 12, see the additional instructions in the Quick Start for GEO Clustering for SUSE Linux Enterprise High Availability Extension. It is available at http://www.suse.com/documentation/. Refer to the section Upgrading from SLE HA 11 SP3 to SLE HA 12.

Note: Reverting after Upgrade

After the upgrade process to product version 12, reverting back to product version 11 is not supported.

D.3 Updating Software Packages on Cluster Nodes #

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

Does the update affect any packages belonging to SUSE Linux Enterprise High Availability Extension or he 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 #  systemctl stop pacemaker.service
```
Does the package update require a reboot? If yes: Stop the cluster stack on the node before starting the software update:
```
root #  systemctl stop pacemaker.service
```

If none of the situations above do 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”.

Warning: Active Cluster Stack During Update

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.

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

root # crm configure property maintenance-mode=true

or restart the cluster stack on the respective node with:

root #  systemctl start pacemaker.service

D.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