The Trilio appliance of T4O 4.2 is running a different Kernel than the Trilio appliance for T4O 4.1 or older.
When upgrading from T4O 4.1 or older it is recommended to replace the Trilio appliance entirely and not do an in-place upgrade. This document provides both online/offline upgrades of Trilio Appliance from any of the older TVO-4.2-based releases to the latest TVO-4.2 release.
The prerequisites should already be fulfilled from upgrading the Trilio components on the Controller and Compute nodes.
Please ensure to complete the upgrade of all the Trilio components on the Openstack controller & compute nodes before starting the rolling upgrade of Trilio.
The mentioned Gemfury repository should be accessible from Trilio VM.
Either 4.2 GA OR any hotfix patch against 4.2 should be already deployed for performing upgrades mentioned in the current document.
Please ensure the following points before starting the upgrade process:
No snapshot OR restore to be running.
Global job-scheduler should be disabled.
wlm-cron should be disabled and any lingering process should be killed.
The following sets of commands will disable the wlm-cron service and verify that it is has been completly shut-down.
hf_upgrade.sh
script on all T4O nodes where the upgrade is to be done.You can check the usage of this script here.
Either perform the Step 1.1 Upgrade to the latest Hotfix/Maintenance release
or
1.2 Upgrade to the intermediate Hotfix/Maintenance release
depending on your requirement.
a. Download the hf_upgrade.sh
of desired Hotfix/Maintenance release
You have to replace the Gitbranch
in below command with the actual branch name of the Hotfix/Maintenance release you wish to upgrade.
You will get that git branch name from Release Notes page of that particular Hotfix/Maintenance release
b. Edit downloaded hf_upgrade.sh
and set the BRANCH_NAME
as triliodata-hotfix-4-2
for any Hotfix/Maintenance release and OFFLINE_PKG_NAME
must be set to particular hotfix package name
You would find the offline package name for particular release at http://repos.trilio.io:8283/triliodata-hotfix-4-2/offlinePkgs/
For example, if you wish to upgarde to 4.2.7 release then BRANCH_NAME would be triliodata-hotfix-4-2
and OFFLINE_PKG_NAME must be set to 4.2.7-offlinePkgs.tar.gz
in the script.
Here the packages need to be downloaded on a separate host which has internet access.
The script ./hf_upgrade.sh
can be used with the below-mentioned option to download the required package
hf_upgrade.sh
script on a separate host which has internet accessUse this script to download the upgraded packages.
You can check the usage of this script here.
Either perform the Step 1.1 Upgrade to the latest Hotfix/Maintenance release
or 1.2 Upgrade to the intermediate Hotfix/Maintenance release
depending on your requirement.
a. Download the hf_upgrade.sh
of desired Hotfix/Maintenance release
You have to replace the Gitbranch
in below command with the actual branch name of the Hotfix/Maintenance release you wish to upgrade.
You will get that git branch name from Release Notes page of that particular Hotfix/Maintenance release
b. Edit downloaded hf_upgrade.sh
and set the BRANCH_NAME
as triliodata-hotfix-4-2
for any Hotfix/Maintenance release and OFFLINE_PKG_NAME
must be set to particular hotfix package name and then run the script.
You would find the offline package name for particular release at http://repos.trilio.io:8283/triliodata-hotfix-4-2/offlinePkgs/
For example, if you wish to upgarde to 4.2.7 release then BRANCH_NAME would be triliodata-hotfix-4-2
and OFFLINE_PKG_NAME must be set to 4.2.7-offlinePkgs.tar.gz
in the script.
4.2-offlinePkgs.tar.gz
package and hf_upgrade.sh
script to all the Trilio nodesVerify all wlm services on all Trilio nodes
Make sure all wlm services are up and running from python version 3.8.x
Check the mount point using “df -h” command
Grafana dashboard shows the correct wlm service status on all T4O nodes.
Enable Global Job Scheduler
Additional check for wlm-cron on the primary node
Red Hat OpenStack, TripleO, and Kolla Ansible Openstack are using the nova UID/GID of 42436 inside their containers instead of 162:162 which is the standard in other Openstack environments.
Please verify that the nova UID/GID on the Trilio Appliance is still 42436, to do so follow the below document provided here: