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

10 Upgrading to the Latest Product Version

For general instructions on how to upgrade a cluster, see Chapter 5, Upgrading Your Cluster and Updating Software Packages. The chapter also describes which preparations to take care of before starting the upgrade process.

Table 10.1: Supported Upgrade Paths for SLE HA and SLE HA Geo

Upgrade From ... To

Upgrade Path

For Details See

SLE HA 11 SP3 to SLE HA (Geo) 12

Offline Migration

  • Base System: SUSE Linux Enterprise Server 12 Deployment Guide, part Updating and Upgrading SUSE Linux Enterprise

  • SLE HA: Administration Guide for SUSE Linux Enterprise High Availability Extension 12, chapter Upgrading Your Cluster and Updating Software Packages, section Offline Migration

  • SLE HA Geo: Offline Migration (New Booth Mechanism)

SLE HA (Geo) 11 SP4 to SLE HA (Geo) 12 SP1

Offline Migration

  • Base System: SUSE Linux Enterprise Server 12 SP1 Deployment Guide, part Updating and Upgrading SUSE Linux Enterprise

  • SLE HA: Administration Guide for SUSE Linux Enterprise High Availability Extension 12 SP1, chapter Upgrading Your Cluster and Updating Software Packages, section Offline Migration

  • SLE HA Geo: Cluster Node and Arbitrator Upgrade

SLE HA (Geo) 12 to SLE HA (Geo) 12 SP1

Rolling Upgrade

  • Base System: SUSE Linux Enterprise Server 12 SP1 Deployment Guide, part Updating and Upgrading SUSE Linux Enterprise

  • SLE HA: Administration Guide for SUSE Linux Enterprise High Availability Extension 12 SP1, chapter Upgrading Your Cluster and Updating Software Packages, section Rolling Upgrade

  • SLE HA Geo: Cluster Node and Arbitrator Upgrade

SLE HA (Geo) 12 SP1 to SLE HA (Geo) 12 SP2

Rolling Upgrade

  • Base System: SUSE Linux Enterprise Server 12 SP2 Deployment Guide, part Updating and Upgrading SUSE Linux Enterprise

  • SLE HA: Administration Guide for SUSE Linux Enterprise High Availability Extension 12 SP2, chapter Upgrading Your Cluster and Updating Software Packages, section Rolling Upgrade

  • SLE HA Geo: Cluster Node and Arbitrator Upgrade

  • DRBD 8 to DRBD 9: Administration Guide for SUSE Linux Enterprise High Availability Extension 12 SP2, chapter DRBD, section Migrating from DRBD 8 to DRBD 9

SLE HA (Geo) 12 SP2 to SLE HA (Geo) 12 SP3

Rolling Upgrade

  • Base System: SUSE Linux Enterprise Server 12 SP3 Deployment Guide, part Updating and Upgrading SUSE Linux Enterprise

  • SLE HA: Administration Guide for SUSE Linux Enterprise High Availability Extension 12 SP3, chapter Upgrading Your Cluster and Updating Software Packages, section Rolling Upgrade

  • SLE HA Geo: Cluster Node and Arbitrator Upgrade

SLE HA (Geo) 12 SP3 to SLE HA (Geo) 12 SP4

Rolling Upgrade

  • Base System: SUSE Linux Enterprise Server 12 SP4 Deployment Guide, part Updating and Upgrading SUSE Linux Enterprise

  • SLE HA: Administration Guide for SUSE Linux Enterprise High Availability Extension 12 SP4, chapter Upgrading Your Cluster and Updating Software Packages, section Rolling Upgrade

  • SLE HA Geo: Cluster Node and Arbitrator Upgrade

SLE HA (Geo) 12 SP4 to SLE HA (Geo) 12 SP5

Rolling Upgrade

  • Base System: SUSE Linux Enterprise Server 12 SP5 Deployment Guide, part Updating and Upgrading SUSE Linux Enterprise

  • SLE HA: Administration Guide for SUSE Linux Enterprise High Availability Extension 12 SP5, chapter Upgrading Your Cluster and Updating Software Packages, section Rolling Upgrade

  • SLE HA Geo: Cluster Node and Arbitrator Upgrade

10.1 Offline Migration (New Booth Mechanism)

The booth version (v0.1) in SUSE Linux Enterprise High Availability Extension 11 to 11 SP3 was based on the Paxos algorithm. The booth version (v0.2) in SUSE Linux Enterprise High Availability Extension 11 SP4 and SUSE Linux Enterprise High Availability Extension 12 and 12 SPx is loosely based on raft and is incompatible with the one running v0.1. Therefore, a rolling upgrade from any system running the old booth version to one running the new booth version is not possible. Instead, all cluster nodes must be offline and the cluster needs to be migrated as a whole as described in Procedure 10.1, “Performing a Cluster-wide Offline Migration”.

Because of the new multi-tenancy feature, the new arbitrator init script cannot stop or test the status of the Paxos v0.1 arbitrator. On upgrade to v0.2, the arbitrator will be stopped, if running. The OCF resource-agent ocf:pacemaker:booth-site is capable of stopping and monitoring the booth v0.1 site daemon.

Procedure 10.1: Performing a Cluster-wide Offline Migration
  1. For an upgrade of the cluster nodes, follow the instructions in the Administration Guide, chapter Upgrading Your Cluster and Updating Software Packages, section Offline Migration.

  2. If you use arbitrators outside of the cluster sites:

    1. Upgrade each arbitrator to the desired SUSE Linux Enterprise Server version. To find the details for the individual upgrade processes, see Table 10.1, “Supported Upgrade Paths for SLE HA and SLE HA Geo”.

    2. Add the Geo clustering extension and install the packages as described in the Riferimento rapido per Geo Clustering.

  3. As the syntax and the consensus algorithm for booth has changed, you need to update the booth configuration files to match the latest requirements. Previously you could optionally specify expiry time and weights by appending them to the ticket name with a semicolon (;) as separator. The new syntax has separate tokens for all ticket options. See Chapter 4, Setting Up the Booth Services for details. If you did not specify expiry time or weights different from the defaults, and do not want to use the multi-tenancy feature, you can still use the old /etc/booth/booth.conf.

  4. Synchronize the updated booth configuration files across all cluster sites and arbitrators.

  5. Start the booth service on the cluster sites and the arbitrators as described in Section 4.5, “Enabling and Starting the Booth Services”.

10.2 Cluster Node and Arbitrator Upgrade

  1. For an upgrade of the cluster nodes, follow the instructions in the Administration Guide, chapter Upgrading Your Cluster and Updating Software Packages.

  2. If you use arbitrators outside of the cluster sites, proceed as follows for each arbitrator:

    1. Perform an upgrade to the desired target version of SUSE Linux Enterprise Server. To find the details for the individual upgrade processes, see Table 10.1, “Supported Upgrade Paths for SLE HA and SLE HA Geo”.

    2. Add the Geo clustering extension and install the packages as described in Riferimento rapido per Geo Clustering.

Print this page