Step E: Upgrade nodes
Upgrade the worker nodes
Perform these steps on each worker node in the cluster, after you've removed all the nodes from the cluster.
Before you start, make sure that you have performed the tasks in Step B: Prepare each AWS Elemental Conductor Live node for migration.
-
Create a backup of the database on the node. See Backing up data.
-
Set boot mode on the node to UEFI. See Switching boot mode to UEFI.
-
Perform a kickstart to upgrade the operating system to RHEL 9. See Installing RHEL 9.
-
Install Elemental Live version 2.26.x on the node. See Installing Elemental Live on a worker node.
-
Restore the database onto the node. See Restoring the database.
-
Install new licenses.
If a specific node handles SMPTE 2110 inputs or outputs, you should have obtained a new license that includes the SMPTE 2110 add-on package. (The procedure for obtaining a new license is described in the essential notes in the current Release Notes.) To deploy the license, see the section about configuring licenses in the AWS Elemental Live Configuration Guide.
Each worker node now has the new operating system and software installed, and it restored to its former database, including most of its configuration data.
Upgrade the Conductor nodes
Perform these steps on both Conductor nodes.
-
Set boot mode on the node to UEFI. See Switching boot mode to UEFI.
-
Perform a kickstart to upgrade the operating system to RHEL 9. See Backing up data.
-
Install Conductor Live version 3.26.1 on the node. See Installing Conductor Live on nodes.
-
Restore the database onto each node. See Restoring the database.
The primary Conductor node now has all the configuration information about the cluster. This means that when you add worker nodes back into the cluster, all the information about redundancy groups, for example, is present on the primary Conductor node. You don't have to set it up again.
-
If you moved custom files to a safe location as part of your preparation, you can now copy these files back to their original location.
