Step A: Get ready - AWS Elemental Conductor Live
Read the essential notesModify your automation systemVerify installer typeCreate a boot USB driveObtain the default elemental passwordVerify space on each node

Step A: Get ready

Read the essential notes

Refer to the essential notes in the current Release Notes to identify key changes to the behavior of the Conductor Live and worker nodes.

Important

Make sure that you have the latest version of the Release Notes. If you downloaded the file more than a few days ago, we recommend that you download it again.

Follow the instructions in the Release Notes to prepare for these changes. Make a note of all the decisions that you make, particularly:

  • If you have Elemental Live nodes that have a Mellanox NIC, you must decide whether you will include the –skip-mellanox option in the install command on the node.

  • If you have Elemental Live nodes that handle SMPTE 2110 inputs or outputs, you must a new license for each. The procedure for obtaining a new license is described in the essential notes.

Modify your automation system

In order for processing to continue after you split the cluster, you must make changes to the way your automation system and your web interface users connect to the cluster.

Set up automation system to use physical IP addresses

After you split the cluster, the primary Conductor is accessible only via its physical IP address, while the secondary Conductor is accessible via the VIP (and also via its physical IP address). By comparison, when the cluster is set up in the normal way, the primary Conductor is accessible via the VIP, while the secondary Conductor isn't accessible.

Therefore you must make sure that your automation system can connect to the primary Conductor via that node's physical IP address.

Plan the new connection for the primary Conductor. Then switch over to the new way of connecting right after you split the cluster.

Set up users to use physical IP addresses

The users of the Conductor Live web interface must enter the physical IP address of the appropriate Conductor node. Remember to provide them with that address at the same time as you switch over the automation system.

Set up automation system to use permalinks

You must make sure that your automation system isn't referencing resources using an ID. For example, if you use profile IDs to reference profiles, you should instead use permalinks. Perform this setup before you start the first maintenance window.

Note that when you make this change, the cluster will be in line with existing AWS Elemental best practice.

Set up automation system to use HTTPS

After a node has been migrated, it uses HTTPS. By default, the nodes are set up with self-signed certificates. Make sure of the following points:

  • You might need to change your automation system to use HTTPS.

  • In addition, if you decide not to provide custom certificates, use HTTPS with the -k option.

Verify installer type

For Elemental Live, the software installer that you use depends on whether you have GPU-accelerated software type, or CPU-only. To determine the type of software, look at any page on the web interface of each worker node. At the top, look for these icons:

  • CPU and GPU icons: the software is GPU-accelerated.

  • CPU icon only: the software is CPU-only.

Make a note of the installer type for every Elemental Live node in the cluster.

Create a boot USB drive

On Dell hardware, you have the option to install RHEL 9 by using a boot USB drive or by using or iDRAC (for Dell). (Note that SuperMicro hardware, you can only install RHEL 9 by using IPMI.)

If you want to use a boot USB drive with Dell, you should make the drive now. You might want to make several drives, depending on how many people will be performing the migration tasks. For instructions, see Create a boot USB drive.

Obtain the default elemental password

When you install RHEL 9, the elemental password will be reset to the global default value. When you install the AWS Elemental software, you will need to enter this default password.

If your organization had previously kickstarted an AWS Elemental appliance, someone in your organization might have the global default password. Note that this global default password isn't the same as the unique default password that applied when you first obtained the appliance.

If you need help finding the password, go to the AWS Elemental Support Center, and read the Knowledge article Unique passwords for AWS Elemental appliances or open a case.

Verify space on each node

As part of the upgrade, you create a backup of the data on each node. You must make sure that you have enough free space for the backup. Follow these guidelines:

  • The backup for a freshly kickstarted and licensed appliance generates a 5 MB backup directory and a 2 MB zipped version of the backup (<hostname>_lifeboat-archive.zip).

  • Your configuration will generate larger files because of the data that you create, so review available space before starting.

  • Check the contents of the /home partition, and clear out old files, unnecessary files, and old installers.