Offline Update

If you do not allow internet access, then you must complete offline updates of Turbonomic. When you complete the update, the system automatically unmounts the ISO image. To update MariaDB, your Turbonomic instance must be mounted on the same ISO image that you used to update it to version 8.3.5 or later.

To perform an offline update of your Turbonomic installation:

Run the upgrade-precheck.sh script.

This script ensures that your current installation of Turbonomic is ready to update and it must be run before going on to update your installation (see Checking Before Updating).
Save a snapshot of your current Turbonomic VM.

Before updating, shut down (not power off) the Turbonomic VM.
```
sudo init 0
```
Then, perform a snapshot (or clone the VM). This provides a reliable restore point you can turn to in the event that trouble occurs during the update. After you have the snapshot, bring the VM back online.
Optionally, enable new probes in your environment.

Note:
As Turbonomic evolves, the set of delivered probes change. Also, from one version to the next, the set of probes that are enabled by default can change. When you update to a new version, the update does not change your probe configuration. An update to a newer version does not automatically enable any new probes in your deployment. If you want to take advantage of new probes in an update, then you must enable them manually.

For steps to enable new probes in your updated version, see Enabling and Disabling Probe Components. Use these steps to edit the platform's cr.yaml file.

Note:
During the online or offline upgrade process, you should not apply these changes at this time.
Download the ISO image.

Refer to the email you received from IBM for links to the Turbonomic OVA file and to the ISO image.
Save the ISO image to a location that is available to the VM that runs Turbonomic. Then mount the image as a CD drive.

For example, if you run the Turbonomic VM in vCenter Server do the following:
1. In vCenter, navigate to the Turbonomic VM.
2. Right-click the VM and choose Edit Settings.
3. In the CD/DVD Drive drop-down menu, select Datastore ISO, then browse to the Turbonomic update ISO image and choose it.
4. Ensure that Connect at power on is selected.
Open an SSH terminal session to your Turbonomic instance.

Log in with the System Administrator that you set up when you installed Turbonomic:
- Username: turbo
- Password: [your_private_password]
Mount the ISO to your Turbonomic appliance.

Ensure that the VM is mounted on the Turbonomic update ISO image. To update MariaDB, your Turbonomic instance must be mounted on the same ISO image that you used to update it to version 8.3.5 or later. The MariaDB script pulls the necessary RPMs and updates the database.
```
sudo mount /dev/cdrom /mnt/iso |& tee -a $HOME/Turbonomic_MariaDB_upgrade.log
```
Get the script for your update version.

On your local machine, navigate to where you want to download the script. Run the following command as a single line command:
```
curl -O --proxy PROXY_NAME_IP:PORT https://download.vmturbo.com/appliance/download/updates/<VNUM>/isoUpdate.sh
```
Where
- --proxy PROXY_NAME_IP:PORT is an optional specification to execute the download through a proxy.
- <VNUM> is the version you are updating to. The version must be 8.2.5 or later.
Upload the script to your Turbonomic instance.

Initiate a file transfer from your local machine to the Turbonomic server. Save the script to /opt/local/bin/ on the VM that runs Turbonomic.
Make the script executable.
```
chmod +x /opt/local/bin/isoUpdate.sh
```
Run the offline installation.
```
/opt/local/bin/isoUpdate.sh
```
As the script runs, it:
- Backs up the old scripts in your installation.
- Updates the configuration and code assets in your installation.
- Updates the platform to the new version.
- Updates custom resources.
- Updates the MariaDB configuration (but this does not update the MariaDB version).
- If you have enabled Embedded Reports or Data Export, installs the Embedded Reports and Data Export database (Postgres and TimescaleDB).
- Scales down the t8c-operator and the Turbonomic components.
- Executes the final updates for this version.
- Scales up the t8c-operator, which then restarts the Turbonomic components.
After the script is finished updating your platform, give it enough time for all the components to start up again.

Verify that the Turbonomic application installed correctly.

kubectl get pods -n turbonomic

After all of the pods start, the READY column should read 1/1, 2/2, and so on and the STATUS column should read Running for each pod.

The output is similar to the following example:

NAME                                         READY   STATUS    RESTARTS 
action-orchestrator-b6454c9c8-mfl85          1/1     Running   0         
api-7887c66f4b-shndq                         1/1     Running   0         
auth-5b86976bc8-vxwz4                        1/1     Running   0         
clustermgr-85548678d9-r5wb8                  1/1     Running   0         
...

Verify that you are running the correct version of MariaDB.

For this version of the product, Turbonomic supports MariaDB, version 10.5.23. Even after updating to this Turbonomic version, it is possible that your installation is running an earlier version of MariaDB.
1. While still in the SSH session, check the MariaDB version.
```
mysql -V
```
  The output is similar to the following example:
```
mysql  Ver 15.1 Distrib 10.5.23-MariaDB, for Linux (x86_64) using readline 5.1
```
2. If the MariaDB version is earlier than 10.5.23, update your MariaDB.
  
  Before you run the script, you need to know the MariaDB password. By default, this password is vmturbo.
```
sudo /opt/local/bin/mariadbUpgrade.sh |& tee -a $HOME/Turbonomic_MariaDB_upgrade.log
```
  The script updates the version of MariaDB. It also increases size limits for the allowed packets, and buffer and log sizes for the innodb. The script output includes the following (where Total Memory and buffer pool size can vary depending on your VM configuration):
```
================================
Update the mariadb configuration
================================
Total Memory: 128773 MB
Changing Innodb buffer pool size to: 9216 MB
Changing max allowed packets to: 1G
Changing innodb log file size to: 10G
================================
```
3. When the script completes, verify that the correct version of MariaDB is running.
```
mysql -V
```

Scale up the Turbonomic platform's pods.

To update the database, the script scales down your platform pods. When it completes, the script displays the following prompt:

##########################################################################
When confirmed the mariadb has been upgraded and is properly working, run:
kubectl scale deployment --replicas=1 t8c-operator -n turbonomic
##########################################################################

After you verify that the correct version of MariaDB is running, scale up the platform.

kubectl scale deployment --replicas=1 t8c-operator -n turbonomic

Unmount the ISO file.

sudo umount /mnt/iso |& tee -a $HOME/Turbonomic_MariaDB_upgrade.log

Clear your browser data and refresh your browser.

After clearing the browser data and refreshing your browser, you have full access to Turbonomic features. However, features that rely on current analysis data will not be available until after a full market cycle — usually 10 minutes. For example, the Pending Actions charts will not show any actions until after a full market cycle.
Notify other users to clear their browser data and refresh their Turbonomic browser sessions.