10 Upgrading to the Latest Product Version #
For general instructions on how to upgrade a cluster, see Chapter 24, Upgrading Your Cluster and Updating Software Packages. The chapter also describes which preparations to take care of before starting the upgrade process.
|
Upgrade From ... To |
Upgrade Path |
For Details See |
|---|---|---|
|
SLE HA 11 SP3 to SLE HA (Geo) 12 |
Cluster Offline Upgrade |
|
|
SLE HA (Geo) 11 SP4 to SLE HA (Geo) 12 SP1 |
Cluster Offline Upgrade |
|
|
SLE HA (Geo) 12 to SLE HA (Geo) 12 SP1 |
Cluster Rolling Upgrade |
|
|
SLE HA (Geo) 12 SP1 to SLE HA (Geo) 12 SP2 |
Cluster Rolling Upgrade |
|
|
SLE HA (Geo) 12 SP2 to SLE HA (Geo) 12 SP3 |
Cluster Rolling Upgrade |
|
|
SLE HA (Geo) 12 SP3 to SLE HA (Geo) 12 SP4 |
Cluster Rolling Upgrade |
|
|
SLE HA (Geo) 12 SP4 to SLE HA (Geo) 12 SP5 |
Cluster Rolling Upgrade |
|
10.1 Cluster Offline Upgrade (New Booth Mechanism) #
The booth version (v0.1) in SUSE Linux Enterprise High Availability 11 to 11 SP3 was based on the Paxos algorithm. The booth version (v0.2) in SUSE Linux Enterprise High Availability 11 SP4 and SUSE Linux Enterprise High Availability 12 and 12 SPx is loosely based on raft and is incompatible with the one running v0.1. Therefore, a cluster 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 Offline Upgrade”.
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.
For an upgrade of the cluster nodes, follow the instructions in the Administration Guide, chapter Upgrading Your Cluster and Updating Software Packages, section Cluster Offline Upgrade.
If you use arbitrators outside of the cluster sites:
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”.
Add the Geo clustering extension and install the packages as described in the Geo Clustering Quick Start.
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.Synchronize the updated booth configuration files across all cluster sites and arbitrators.
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 #
For an upgrade of the cluster nodes, follow the instructions in the Administration Guide, chapter Upgrading Your Cluster and Updating Software Packages.
If you use arbitrators outside of the cluster sites, proceed as follows for each arbitrator:
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”.
Add the Geo clustering extension and install the packages as described in Geo Clustering Quick Start.