Updating Turbonomic
IBM continually and rapidly innovates and improves all aspects of this product. IBM releases newer versions of this product every two weeks. You should check regularly to see if a new version is available by visiting the IBM Turbonomic documentation site.
When a new version is available, it is important to properly update your existing installed instance. When you first installed Turbonomic, you put into place sophisticated data collection and analysis processes, and your database retains performance data from across your virtual environment. Turbonomic uses this historical data for optimization, projecting trends, and other analysis. This means that the database is important to Turbonomic and becomes more so over time. Properly updating your installation of Turbonomic preserves the database for continued use.
For updates from the 7.21.x family or earlier, contact your Turbonomic representative.
Starting with Turbonomic version 8.7.5, IBM Container Registry is used for all Turbonomic images for online upgrades. Refer to your preferred update method for more information.
OVA updates
Before you begin the update procedure:
-
Review What's New and Release Notes to see what is new for this release.
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.
-
Make sure you have the email that IBM sent to you with links to the Turbonomic
OVA
file and to the ISO image. -
For on-prem installations, make sure that the physical machine hosting the VM meets the minimum requirements (see Minimum Requirements).
Note:Before updating Turbonomic, you must extend the
/var
partition to at least 340 GB. If the/var
partition requirement is not met, your upgrade may fail, new container images may not load properly, and you can run into an ImagePullBackOff issue for some of the images. Before upgrading, be sure that the partition has sufficient disk space. If you need to free up disk space to increase the size of the partition, you can delete old images that are not in use. For details, see Increasing Available Disk Space. -
Ensure you are running the correct version of the historical database.
For its historical database, Turbonomic supports long-term maintenance stable series of MariaDB (the minimum supported version is 10.6) and MySQL 8.0.x. This support includes comprehensive testing and quality control for Turbonomic usage.
For more information, see Verifying your MariaDB Version.
-
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).
Update your Turbonomic VM using either of the following methods:
Online method, if you have access to the internet:
See Online UpdateOffline method, via a downloaded ISO image:
See Offline Update
Red Hat OpenShift updates
-
If you are running Turbonomic on Red Hat OpenShift, see Updating using the Red Hat OpenShift OperatorHub.