Skip to content

Guide

Goal

Safely upgrade to the latest Altair SLC Hub.

Prerequisites

  • Administrator access to the Altair SLC Hub.
  • Administrator access to the Altair SLC Hub server and worker machines.
  • Administrator access to the database and S3 store.
  • Access to the RPM Files.

Preparation

The upgrade process is fully automated by standard usage of DNF and RPM packages. There should be no need to manually save and restore files. Before upgrading, backup the contents of the etc directory in the Altair SLC Hub installation directory.

The upgrade process is fully automated by the Windows MSI installer. There should be no need to manually save and restore files. Before upgrading, backup the contents of the etc directory in the Altair SLC Hub installation directory.

Before continuing, to prevent any data loss ensure that all users log out from the Altair SLC Hub, including those logged in to the Altair SLC Hub portal from a browser and those logged in from Altair Analytics Workbench.

All Deployment API endpoints need to be deactivated. To do this, in the Altair SLC Hub portal launch Deployment Services and then click Deployments. Select all Deployment API endpoints and click Deactivate selected. Ensure you select the required published libraries on all pages in the Deployments list and in all Namespaces.

All Published Libraries need to be deactivated. To do this, in the Altair SLC Hub portal launch Enterprise and click Manage Published Libraries. Select all Published Libraries and click Deactivate selected. Ensure you select the required published libraries on all pages in the Manage Published Libraries list and in all Namespaces.

Now stop Altair SLC Hub and all workers using the following commands on each machine in turn:

hubctl service stop
Ensure that all Altair SLC Hub services on all the machines have stopped using the hubctl command:
hubctl service status

Backup the database

It is recommended that the database is backed up following your standard recovery procedures.

If backup procedures are not in place yet, the PostgreSQL utility pg_dump can be used. The details for the database connection can be found using the following hubctl command:

hubctl config print database

Information to backup the internal database is given here.

Backup object store

It is recommended that the object store is backed up following your standard recovery procedures.

Information to backup the internal object store is given here.

Backup all configuration

For all the Altair SLC Hub server and worker machines, backup the configuration by taking a copy of the etc directory.

Server and Worker node installed on the same machine

If your installation includes a Server and Worker installed on the same machine, you need only follow Upgrading the Server and Worker node on the same machine. If not, you should follow Upgrading the Server and Upgrading Worker Nodes seperately.