(Important) Verifying your MariaDB Version

Turbonomic supports using MariaDB version 10.5.20 and MySQL 8.0.x for the historical database. This support includes comprehensive testing and quality control for Turbonomic usage.

If you are running Turbonomic installed as a VM image (OVA or VHD), and using the database that is included in that image installation, then you must use version 10.5.20. If you are updating your version of Turbonomic (instead of installing it for the first time), ensure that you are using the correct version of MariaDB with your installation.

Important:

It is a requirement that you run MariaDB version 10.5.20 or later. Turbonomic can operate with other versions of MariaDB; however, it is fully tested to operate with MariaDB version 10.5.20.

Because of a known issue, you must never use MariaDB versions 10.5.14, 10.5.15, or 10.6.7.

When you initially installed Turbonomic, that installation included MariaDB running a specific version. As you update your Turbonomic version, the MariaDB version remains the same. The first release of Turbonomic that included MariaDB 10.5.20 is 8.7.6. If you initially installed an earlier version, and did not update your MariaDB to 10.5.20, then you must do it now.

  • For VM image installations, it is possible to configure the installation to use a remote database (external to the VM). If you are using a remote MariaDB instance, use version 10.5.20. For a remote MySQL, use version 5.7.x or 8.0.x. See Configuring an External MySQL Database.

  • For installations on a Kubernetes cluster (not deployed as a Turbonomic VM image), if you are using MariaDB use version 10.5.20; however, MariaDB 10.2 for Azure DB Services is tolerated. You can find a download package at: https://archive.mariadb.org/mariadb-10.5.20/yum/centos7-amd64. For a remote MySQL, use version 5.7.x or 8.0.x. See Configuring an External MySQL Database.

Checking your MariaDB Version

Check the version of MariaDB running on your Turbonomic OVA.

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

  2. Check the MariaDB version.

    mysql -V

    The output is similar to the following example:

    mysql  Ver 15.1 Distrib 10.5.20-MariaDB, for Linux (x86_64) using readline 5.1

If the version is earlier than 10.5.20-MariaDB, then you must update your database.

If your version is equal to or greater than 10.5.20-MariaDB do not complete the update steps.

Updating your MariaDB

If you are using Turbonomic installed as a VM image, and you are using the default MariaDB that was installed with that image, you must run MariaDB version 10.5.20.

Important:

Before you complete these steps, you must update Turbonomic to the latest version using the update script.

Using the update script installs the necessary MariaDB update scripts. If your current version of Turbonomic is earlier than 8.3.5, then update your installed version before running these steps. For instructions to use the product update script, see Updating Turbonomic to a New Version.

If your current Turbonomic version is earlier than 8.3.5 and you want to update MariaDB but you do not want to update Turbonomic, contact your support representative.

To update your MariaDB on your Turbonomic VM:

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

  2. (Offline updates only) Ensure that the VM is mounted on the Turbonomic update ISO image.

    Note:

    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.

    If you complete an offline update and mount the ISO image, you can skip step 3 since the mariadbUgrade.sh is on the ISO image.

    For more information, see Offline Update.

  3. (Online updates only) Set up the MariaDB update script.

    1. Log in to the Turbonomic VM.

      Use SSH to log in to the Turbonomic VM that uses the Turbonomic account and password.

    2. Change to the scripts directory.

      cd /opt/local/bin
    3. Get the latest version of the script.

      curl -O --proxy PROXY_NAME_IP:PORT https://raw.githubusercontent.com/turbonomic/t8c-install/master/bin/mariadbUpgrade.sh

      Where --proxy PROXY_NAME_IP:PORT is an optional specification to run the download through a proxy.

      Note:

      (Offline updates only) Download the script to your local machine.

    4. Ensure that the script is saved on the Turbonomic server at /opt/local/bin/mariadbUpgrade.sh.

      Note:

      (Offline updates only) Use a Secure Shell session to upload the script from your local machine to the Turbonomic server.

  4. (Offline updates only) Update the MariaDB script.

    1. Mount the ISO to your Turbonomic appliance.

      sudo mount /dev/cdrom /mnt/iso |& tee -a $HOME/Turbonomic_MariaDB_upgrade.log
    2. Run the MariaDB upgrade script.

      sudo /opt/local/bin/mariadbUpgrade.sh |& tee -a $HOME/Turbonomic_MariaDB_upgrade.log

      The script will pull the necessary RPMs and update the database.

    3. Check the status of the pods. If they are scaled down, scale them up.

      kubectl scale deployment t8c-operator --replicas=1
    4. At the very end, unmount the ISO file.

      sudo umount /mnt/iso |& tee -a $HOME/Turbonomic_MariaDB_upgrade.log
  5. Run the MariaDB update script.

    Before you run the script, you need to know the MariaDB password. By default, this password is vmturbo.

    1. Make the script executable.

      Note:

      If you complete offline updates and ran the offline upgrade script, the updated mariadbUpgrade.sh is copied from the ISO image to the /opt/local/bin directory with the executable flag enabled. You can skip this step and run the script.

      sudo chmod +x /opt/local/bin/mariadbUpgrade.sh
    2. Run the database update script.

      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
    ================================
  6. Verify the updated MariaDB version.

    When the script completes, you are running version 10.5.20. To verify, run:

    mysql -V

    The output is similar to the following example:

    mysql  Ver 15.1 Distrib 10.5.20-MariaDB, for Linux (x86_64) using readline 5.1
  7. 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