Reference: Step-wise offline update

Note:

The process that is described here is applicable only to the OVA deployment model.

Complete the following steps to perform a stepwise offline update of your Turbonomic installation.

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.
Download and attach the ISO image to the VM that runs Turbonomic.

Refer to the email you received from IBM for links to the Turbonomic OVA file and to the ISO image.
Mount the ISO image by logging in to vCenter.
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]
If you are prompted to override the CD-ROM lock, select Yes and click OK to disconnect anyway and override the lock.
Mount the ISO image.
```
sudo mount /dev/cdrom /mnt/iso
```
Verify the correct version of the ISO image is mounted.
```
ls /mnt/iso
```
Verify that the ISO image contains the correct version for your update.
Load the latest images.
```
sudo /mnt/iso/turboload.sh
```
This script loads all the images to the Turbonomic instance.

The output is similar to the following example:
```
The t8c upgrade iso has been mounted
Image check:
============
***************************
All images have been loaded
***************************
```
If the load does not succeed, the script lists any images that did not load, along with instructions to load them manually.
Run the following command as a single line command to update Turbonomic.
```
/mnt/iso/turboupgrade.sh | tee -a $HOME/Turbonomic_MariaDB_upgrade.log
```
Wait until the script is finished.
Verify that you are running the correct version of MariaDB.

For this version of the product, Turbonomic supports MariaDB, version 10.6.19. 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.6.19-MariaDB, for Linux (x86_64) using readline 5.1
```
2. If the MariaDB version is earlier than 10.6.19, 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
```
Unmount the ISO image.
```
sudo umount /dev/cdrom
```
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.
Optionally, enable Turbonomic on Turbonomic.

In Turbonomic, the supply chain can model your deployment as a Business Application. For updates from versions earlier than 7.22.4, you must enable the components that implement this feature.

For steps to enable these components in your updated version, see Enabling and Disabling Probe Components. Use these steps to edit the platform's cr.yaml file, but do not use kubectl to apply those changes yet.

When you update the components in your cr.yaml file, specify the following:
```
kubeturbo:
 enabled: true
prometheus-mysql-exporter:
 enabled: true
 mysql:
  user: root
  pass: vmturbo
prometheus:
 enabled: true
prometurbo:
 enabled: true
```

Verify that Turbonomic installed correctly.

kubectl get pods -n turbonomic

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

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         
...

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.