Generic Pre-requisites

1. Please ensure the following points before starting the upgrade process:

   1. No snapshot OR restore to be running.

   2. Global job scheduler should be disabled.

2. The mentioned gemfury repository should be accessible from TVault VM.

Rolling upgrade on Openstack Ansible

Repo Updates

Add gemfury repo on each dmapi, horizon containers & compute node(s) to get updated packages.

Create a file /etc/apt/sources.list.d/fury.list and add below line in it.

deb [trusted=yes] https://apt.fury.io/triliodata-4-0/ /

Use the below commands to get a list of updated packages available on the configured repositories.

apt-get update
apt list --upgradable 

Upgrade tvault-datamover-api package

• Login to dmapi container from the controller node using the below command.

lxc-attach -n controller_dmapi

• Take a backup of the following file on each dmapi container(s).

tar -czvf dmapi_config.tar.gz /etc/dmapi

• Add the gemfury repo and upgrade the dmapi package using the below command. Select the appropriate package depending on the python version used.

apt install python3-dmapi --upgrade

• Restore the backed-up config files

tar -xzvf dmapi_config.tar.gz -C /

• Now restart and check the service tvault-datamover-api on controller.

systemctl restart tvault-datamover-api
systemctl status tvault-datamover-api

Upgrade Horizon plugin

• For the Horizon plugin upgrade, we need to upgrade below two packages.

python3-tvault-horizon-plugin python3-workloadmgrclient

• Login to the horizon container from the controller node using the below command.

  Copy

  lxc-attach -n controller_horizon_container-ead7cc60

• Add the gemfury repo and upgrade the tvault-horizon-plugin & workloadmgrclient packages using the below command. Select the appropriate package depending on the python version used.

apt install python3-tvault-horizon-plugin --upgrade
apt install python3-workloadmgrclient --upgrade

• Restart the apache2 service and verify the workloadmgrclient version using the below commands.

systemctl restart apache2
workloadmgr --version

Upgrade the tvault-contego package

NFS Storage Backend

• Take a backup of following file on each compute node(s) for nfs storage backend.

tar -czvf  contego_config.tar.gz /etc/tvault-contego/ 

• Upgrade the tvault-contego package using below command.Select the appropriate package depending on python version used.

apt install python3-tvault-contego --upgrade

• Restore the backed-up config files

 tar -xzvf  contego_config.tar.gz -C /

• Now restart and check the service tvault-contego on compute node(s).

systemctl restart tvault-contego
systemctl status tvault-contego

Please make sure all configuration files are unchanged.

S3 Storage Backend

• Take a backup of following file on each compute node(s) for s3 storage backend.

tar -czvf  contego_config.tar.gz /etc/tvault-contego/ /etc/tvault-object-store/

• Upgrade the tvault-contego package using below command. Select the appropriate package depending on the python version used.

apt install python3-tvault-contego python3-s3-fuse-plugin --upgrade

Note*:- If you get prompt while installing, choose the default selection.

• Restore the backed-up config files

 tar -xzvf  contego_config.tar.gz -C /

• Now restart and check the service tvault-contego on compute node(s).

systemctl restart tvault-object-store
systemctl restart tvault-contego 
systemctl status tvault-object-store
systemctl status tvault-contego

Please make sure all configuration files are unchanged.

Rolling upgrade on Kolla Openstack

Upgrade tvault-datamover-api package (trilio_datamover_api Container)

Container trilio_datamover_api needs to be redeployed. Follow below steps on all controller nodes :

• Backup Existing conf files/folders

Copy folders /etc/kolla/nova-api & /etc/kolla/trilio-datamover-api/ to some local location.
Eg. cp -r /etc/kolla/nova-api $HOME/4.0-BK/

• Stop and Remove existing container trilio_datamover_api

docker stop trilio_datamover_api
docker rm trilio_datamover_api

• Pull trilio_datamover_api container image:

## Login to docker using credentials: triliodocker/triliopassword
docker login docker.io

## Pull Trilio Datamover Api container using following command. You need to edit OS_PLATFORM, TVAULT_VERSION,
 OPENSTACK_RELEASE_NAME.

<OS_PLATFORM> could be ubuntu/centos.
<OPENSTACK_RELEASE_NAME> could would be train
<TVAULT_VERSION>    : For exact GA build version check section 1. i) Plan for deployment

docker pull docker.io/trilio/<OS_PLATFORM>-source-trilio-datamover-api:<TVAULT_VERSION>-<OPENSTACK_RELEASE_NAME>

Example command for train openstack on ubuntu platform with triliovault 4.0 release:
docker pull docker.io/trilio/ubuntu-source-trilio-datamover-api:4.0.106-train

• Run datamover api container.

You need to edit OS_PLATFORM, TVAULT_VERSION, OPENSTACK_RELEASE_NAME. 
<OS_PLATFORM> could be ubuntu/centos.
<OPENSTACK_RELEASE_NAME> would be train
<TVAULT_VERSION> : For exact TVAULT build version check section 1. i) Plan for deployment

docker run --network host --name trilio_datamover_api -d --restart always -v /etc/kolla/trilio-datamover-api/nova.conf:/etc/nova/nova.conf \
-v /etc/kolla/trilio-datamover-api/dmapi.conf:/etc/dmapi/dmapi.conf \
-v /var/log/kolla/:/var/log/kolla/ \
trilio/<OS_PLATFORM>-source-trilio-datamover-api:<TVAULT_VERSION>-<OPENSTACK_RELEASE_NAME> /var/lib/kolla/venv/bin/python /usr/bin/dmapi-api 

• Verify deployment

Make sure 'trilio_datamover_api' named container running well and not in 'restarting' state on all controller nodes. 
'docker ps' command can be used for the same.

# docker ps | grep trilio_datamover_api
e603ea78094f  trilio/ubuntu-source-trilio-datamover-api:4.0.106-train   "dumb-init --single-…"   5 minutes ago Up 5 minutes
trilio_datamover_api

Upgrade Horizon Plugin Package

• Login to horizon container (on controller node)

docker exec -it horizon /bin/bash

• Add gemfury repo on horizon to get updated packages.

  Create a file /etc/apt/sources.list.d/fury.list and add below line in it.

  Copy

  deb [trusted=yes] https://apt.fury.io/triliodata-4-0/ /

  Use below commands to get list of updated packages available on repo's.

  Copy

  apt-get update
  apt list --upgradable

• For Horizon plugin upgrade, following packages need to be upgraded.

python3-tvault-horizon-plugin python3-workloadmgrclient

• Run following commands to upgrade the tvault-horizon-plugin & workloadmgrclient packages. Select the appropriate package depending on python version used.

dpkg -l | grep -i tvault
  ii  python3-tvault-horizon-plugin  4.0.92    all   tVault plugin for  OpenStack Horizon Dashboard
  ii  python3-workloadmgrclient      4.0.92   all  tVault Workload Manager Client

apt install python3-tvault-horizon-plugin --upgrade
apt install python3-workloadmgrclient --upgrade

dpkg -l | grep -i tvault
   ii  python3-tvault-horizon-plugin  4.0.115                             all          tVault plugin for  OpenStack Horizon Dashboard
   ii  python3-workloadmgrclient      4.0.115                             all          tVault Workload Manager Client

• Restart docker container (from controller node) and verify the workloadmgrclient version (inside horizon container).

docker restart horizon
docker exec -it horizon /bin/bash
workloadmgr --version

Upgrade Tvault-Contego (trilio_datamover Container)

Container trilio_datamover needs to be redeployed. Follow below steps on all Compute nodes :

• Backup Existing conf files/folders

Copy folder /etc/kolla/trilio-datamover to some local location.
Eg. cp -r /etc/kolla/trilio-datamover $HOME/4.0-BK/

• Stop & remove existing trilio_datamover container

docker stop trilio_datamover
docker rm trilio_datamover

• Pull Trilio Datamover container image using the following command:

## Login to docker using credentials: triliodocker/triliopassword
docker login docker.io

## Pull Trilio Datamover Api container using following command. You need to edit OS_PLATFORM, TVAULT_VERSION,
OPENSTACK_RELEASE_NAME.

<OS_PLATFORM> could be ubuntu/centos.
<OPENSTACK_RELEASE_NAME> would be train
<TVAULT_VERSION> : For exact TVAULT build version check section 1. i) Plan for deployment

docker pull docker.io/trilio/<OS_PLATFORM>-source-trilio-datamover:<TVAULT_VERSION>-<OPENSTACK_RELEASE_NAME>

Example command for train openstack on ubuntu platform with Trilio 4.0 release:
docker pull docker.io/trilio/ubuntu-source-trilio-datamover:4.0.106-train

• Run datamover container.

-- In following docker run command you need to edit OS_PLATFORM, TVAULT_VERSION,
OPENSTACK_RELEASE_NAME.

<OS_PLATFORM> could be ubuntu/centos.
<OPENSTACK_RELEASE_NAME> would be train
<TVAULT_VERSION> : For exact TVAULT build version check section 1. i) Plan for deployment

Note: If your cloud does not use 'ceph' storage for nova/cinder, remove '/etc/ceph' volume mount option 
from below commands.

##If backup storage type is 'NFS'
docker run --privileged --network host --name trilio_datamover -d \
--restart always \
-v /etc/kolla/trilio-datamover/tvault-contego.conf:/etc/tvault-contego/tvault-contego.conf \
-v /etc/kolla/trilio-datamover/nova.conf:/etc/nova/nova.conf \
-v /dev:/dev:rw \
-v /etc/ceph:/etc/ceph:ro \
-v nova_compute:/var/lib/nova/:rw \
-v /var/log/kolla/:/var/log/kolla/ \
-v iscsi_info:/etc/iscsi:rw -v /var/run/libvirt \
trilio/<OS_PLATFORM>-source-trilio-datamover:<TVAULT_VERSION>-<OPENSTACK_RELEASE_NAME> /opt/tvault/start_datamover_nfs

• Verify Deployment of trilio_datamover

Make sure 'trilio_datamover' named container running well and not in 'restarting' state on all compute nodes.
   'docker ps' command can be used for the same.
# docker ps | grep trilio_datamover
3e62813e5ade        trilio/ubuntu-source-trilio-datamover:4.0.115-train   "dumb-init --single-…"   7 hours ago         Up 7 hours                              trilio_datamover

Generic Pre-requisites

1. Please ensure following points before starting the upgrade process:

   1. No snapshot OR restore to be running.

   2. Global job scheduler should be disabled.

2. The mentioned gemfury repository should be accessible from TVault VM.

Rolling upgrade on Openstack Ansible

Repo Updates

Add trilio repo on each dmapi, horizon containers & compute node(s) to get updated packages.

Modify the file /etc/yum.repos.d/trilio.repo and add below line in it.

[trilio]
name=Trilio Repository
baseurl=http://trilio:XpmkpMFviqSe@repos.trilio.io:8283/triliovault-4.0/yum/
enabled=1
gpgcheck=0

Use below commands to get list of updated packages available on repo's.

yum repolist
yum check-upgrade

1.2 Upgrade tvault-datamover-api package

• Login to dmapi container from controller node using below command.

  Copy

  lxc-attach -n controller_dmapi

• Take a backup of following file on each dmapi container(s).

tar -czvf dmapi_config.tar.gz /etc/dmapi

• Add the trilio repo and upgrade the dmapi package using below command.Select the appropriate package depending on python version used.

You can check installed package using below command.

yum list installed | grep dmapi
yum check-update dmapi

• Upgrade the dmapi package using below command.

yum upgrade dmapi

• Restore the backed-up config files

tar -xzvf dmapi_config.tar.gz -C /

• Now restart and check the service tvault-datamover-api on the controller.

systemctl restart tvault-datamover-api
systemctl status tvault-datamover-api

Upgrade Horizon Plugin Package

• We need to upgrade below two packages to upgrade horizon plugin.

tvault-horizon-plugin workloadmgrclient

• Login to horizon container from controller node using below command.

  Copy

  lxc-attach -n controller_horizon_container-3990523e

• Add the trilio repo and upgrade the tvault-horizon-plugin & workloadmgrclient packages using below command.Select the appropriate package depending on python version used.

yum list installed | grep trilio

• Depending on the output of above command upgrade appropriate packages.

yum upgrade tvault-horizon-plugin workloadmgrclient

• Restart the httpd service and verify the workloadmgrclient version using below commands.

systemctl restart httpd
workloadmgr --version

Upgrade Tvault-Contego Package

NFS Storage Backend

• Take a backup of following file on each compute node(s) for nfs storage backend.

tar -czvf  contego_config.tar.gz /etc/tvault-contego/ 

• Add the trilio repo and upgrade the tvault-contego package using below command.Select the appropriate package depending on python version used.

yum list installed | grep tvault

• Depending on the output of above command upgrade appropriate packages.

yum upgrade tvault-contego

• Restore the backed-up config files

 tar -xzvf  contego_config.tar.gz -C /

• Now restart the service tvault-contego. Verify the status of the service and check the mount point.

systemctl restart tvault-contego
systemctl status tvault-contego
df -h

S3 Storage Backend

• Take a backup of following file on each compute node(s) for s3 storage backend.

tar -czvf  contego_config.tar.gz /etc/tvault-contego/ /etc/tvault-object-store/

• Upgrade the tvault-contego and s3fuse-plugin packages using below command. Select the appropriate package depending on the python version used.

 yum upgrade tvault-contego python-s3fuse-plugin-cent7

Note*:- If you get prompt while installing, choose the default selection.

• Restore the backed-up config files

 tar -xzvf  contego_config.tar.gz -C /

• Now restart and check the service tvault-contego on compute node(s).

systemctl restart tvault-object-store
systemctl restart tvault-contego 
systemctl status tvault-object-store
systemctl status tvault-contego
df -h

Rolling upgrade on Kolla Openstack

Upgrade tvault-datamover-api package (trilio_datamover_api Container)

Container trilio_datamover_api needs to be redeployed. Follow below steps on all controller nodes :

• Backup Existing conf files/folders

Copy folders /etc/kolla/nova-api & /etc/kolla/trilio-datamover-api/ to some local location.
Eg. cp -r /etc/kolla/nova-api $HOME/4.0-BK/

• Stop and Remove existing container trilio_datamover_api

docker stop trilio_datamover_api
docker rm trilio_datamover_api

• Pull trilio_datamover_api container image

  Copy

  ## Login to docker using credentials: triliodocker/triliopassword
  docker login docker.io
  
  ## Pull Trilio Datamover Api container using following command. You need to edit OS_PLATFORM, TVAULT_VERSION,
   OPENSTACK_RELEASE_NAME.
  
  <OS_PLATFORM> could be ubuntu/centos.
  <OPENSTACK_RELEASE_NAME> could would be train
  <TVAULT_VERSION>    : For exact GA build version check section 1. i) Plan for deployment
  
  docker pull docker.io/trilio/<OS_PLATFORM>-source-trilio-datamover-api:<TVAULT_VERSION>-<OPENSTACK_RELEASE_NAME>
  
  Example command for train openstack on ubuntu platform with triliovault 4.0 release:
  docker pull docker.io/trilio/centos-source-trilio-datamover-api:4.0.115-train

• Run datamover api container.

  Copy

  You need to edit OS_PLATFORM, TVAULT_VERSION, OPENSTACK_RELEASE_NAME. 
  <OS_PLATFORM> could be ubuntu/centos.
  <OPENSTACK_RELEASE_NAME> would be train
  <TVAULT_VERSION> : For exact TVAULT build version check section 1. i) Plan for deployment
  
  docker run --network host --name trilio_datamover_api -d --restart always -v /etc/kolla/trilio-datamover-api/nova.conf:/etc/nova/nova.conf \
  -v /etc/kolla/trilio-datamover-api/dmapi.conf:/etc/dmapi/dmapi.conf \
  -v /var/log/kolla/:/var/log/kolla/ \
  trilio/<OS_PLATFORM>-source-trilio-datamover-api:<TVAULT_VERSION>-<OPENSTACK_RELEASE_NAME> /var/lib/kolla/venv/bin/python /usr/bin/dmapi-api 

• Verify deployment

  Copy

  Make sure 'trilio_datamover_api' named container running well and not in 'restarting' state on all controller nodes. 
  'docker ps' command can be used for the same.
  
  # docker ps | grep trilio_datamover_api
  e603ea78094f  trilio/centos-source-trilio-datamover-api:4.0.106-train   "dumb-init --single-…"   5 minutes ago Up 5 minutes
  trilio_datamover_api

Upgrade Tvault-Contego (trilio_datamover Container)

Container trilio_datamover needs to be redeployed. Follow below steps on all Compute nodes :

• Backup Existing conf files/folders

Copy folder /etc/kolla/trilio-datamover to some local location.
Eg. cp -r /etc/kolla/trilio-datamover $HOME/4.0-BK/

• Stop & remove existing trilio_datamover container

docker stop trilio_datamover
docker rm trilio_datamover

• Pull Trilio Datamover container image using the following command:

  Copy

  ## Login to docker using credentials: triliodocker/triliopassword
  docker login docker.io
  
  ## Pull Trilio Datamover Api container using following command. You need to edit OS_PLATFORM, TVAULT_VERSION,
  OPENSTACK_RELEASE_NAME.
  
  <OS_PLATFORM> could be ubuntu/centos.
  <OPENSTACK_RELEASE_NAME> would be train
  <TVAULT_VERSION> : For exact TVAULT build version check section 1. i) Plan for deployment
  
  docker pull docker.io/trilio/<OS_PLATFORM>-source-trilio-datamover:<TVAULT_VERSION>-<OPENSTACK_RELEASE_NAME>
  
  Example command for train openstack on ubuntu platform with Trilio 4.0 release:
  docker pull docker.io/trilio/centos-source-trilio-datamover:4.0.106-train

• Run datamover container.

  Copy

  -- In following docker run command you need to edit OS_PLATFORM, TVAULT_VERSION,
  OPENSTACK_RELEASE_NAME.
  
  <OS_PLATFORM> could be ubuntu/centos.
  <OPENSTACK_RELEASE_NAME> would be train
  <TVAULT_VERSION> : For exact TVAULT build version check section 1. i) Plan for deployment
  
  Note: If your cloud does not use 'ceph' storage for nova/cinder, remove '/etc/ceph' volume mount option 
  from below commands.
  
  ##If backup storage type is 'NFS'
  docker run --privileged --network host --name trilio_datamover -d \
  --restart always \
  -v /etc/kolla/trilio-datamover/tvault-contego.conf:/etc/tvault-contego/tvault-contego.conf \
  -v /etc/kolla/trilio-datamover/nova.conf:/etc/nova/nova.conf \
  -v /dev:/dev:rw \
  -v /etc/ceph:/etc/ceph:ro \
  -v nova_compute:/var/lib/nova/:rw \
  -v /var/log/kolla/:/var/log/kolla/ \
  -v iscsi_info:/etc/iscsi:rw -v /var/run/libvirt \
  trilio/<OS_PLATFORM>-source-trilio-datamover:<TVAULT_VERSION>-<OPENSTACK_RELEASE_NAME> /opt/tvault/start_datamover_nfs

• Verify Deployment of trilio_datamover

Make sure 'trilio_datamover' named container running well and not in 'restarting' state on all compute nodes.
   'docker ps' command can be used for the same.
# docker ps | grep trilio_datamover
3e62813e5ade        trilio/centos-source-trilio-datamover:4.0.106-train   "dumb-init --single-…"   7 hours ago         Up 7 hours                              trilio_datamover

Upgrade Horizon Plugin Package

• Login to horizon container

docker exec -it horizon /bin/bash

• Add trilio repo on each controller(s) to get updated packages.

  • Create a file /etc/yum.repos.d/trilio.repo and add below line in it.

    Copy

    [trilio]
    name=Trilio Repository
    baseurl=http://trilio:XpmkpMFviqSe@repos.trilio.io:8283/triliovault-4.0/yum/
    enabled=1
    gpgcheck=0

• Use below commands to get list of updated packages available on repo's.

  Copy

  yum repolist
  yum check-upgrade

• For Horizon plugin upgrade, following packages need to be upgraded.

tvault-horizon-plugin workloadmgrclient

• Select the appropriate package depending on python version used.

 yum list installed | grep trilio

• Depending on the output of above command upgrade appropriate packages

yum upgrade tvault-horizon-plugin workloadmgrclient

• Restart docker container (from controller node) and verify the workloadmgrclient version (inside horizon container).

docker restart horizon
docker exec -it horizon /bin/bash
workloadmgr --version

RedHat Director

Please refer https://triliodata.atlassian.net/wiki/spaces/TRIL/pages/2055864321/Upgrade+of+Trilio+components+on+RHOSP

Starting Trilio for Openstack 4.0 does Trilio for Openstack allow in-place upgrades.

The following versions can be upgraded to each other:

The upgrade process contains upgrading the Trilio appliance and the Openstack components and is dependent on the underlying operating system.

Clone updated triliovault-cfg-scripts github repo

Note: Run all the commands with 'stack' user.

• Clone updated repo\

• If your backup target is Ceph S3 with self signed certs If your backup target is ceph S3 with SSL and SSL certificates are self signed or authorized by private CA, then user needs to provide CA chain certificate to validate the SSL requests. For that, user needs to rename his ca chain cert file to 's3-cert.pem' and copy it into directory - 'triliovault-cfg-scripts/redhat-director-scripts/redhat-director-scripts/puppet/trilio/files'

• Upload triliovault puppet module

• Copy old trilio env file to new repository

Pull latest triliovault container images and update triliovault environment yaml file

Trilio container urls for RHOSP13:

Trilio container urls for RHOSP16:

There are three registry methods available in RedHat Openstack Platform.

1. Remote Registry 2. Local Registry 3. Satellite Server

Identify which method you are using. Below we have explained all three methods to pull and configure trilioVault's container images for overcloud deployment.

Remote Registry:

If you are using 'Remote Registry' method follow this section. You don't need to pull anything. You just need to populate following container urls in trilio env yaml.

• If it’s RHOSP13, populate 'trilio_env.yaml' file with triliovault container urls. Changes looks like following.\

• If it’s RHOSP16, populate 'trilio_env_osp16.yaml' file with triliovault container urls. Changes looks like following.\

Registry on Undercloud:

If you are using 'local registry' on undercloud, follow this section.

Note: Run following script from undercloud node with 'stack' user

• If it’s RHOSP13, run following script. Script, pulls the triliovault containers and updates the triliovault environment file with urls.

• If it’s RHOSP13, user needs to set horizon image url to triliovault horizon image url in overcloud_images.yaml. Changes looks like following.

• If it’s RHOS16, run following script. Script, pulls the triliovault containers and updates the triliovault environment file with urls.\

## Above script pushes trilio container images to undercloud registry and sets correct trilio images urls in trilio_env_osp16.yaml. Verify the changes using following command.

Registry on Redhat Satellite Server

If you are using 'Satellite Server' for container registry, follow this section.

Following are the pull urls for Trilio containers. You need to pull these containers on Redhat Satellite that you already have.

Trilio container urls for RHOSP13:

Trilio container urls for RHOSP16:

• Pull above containers as per your RHOSP release and push to redhat satellite server. For this, you can follow process same as other openstack containers.

• After this, if it’s RHOSP13, populate 'trilio_env.yaml' file with the urls. Changes looks like following.

• If it’s RHOSP13, user needs to set horizon image url to triliovault horizon image url in overcloud_images.yaml. Changes looks like following.

• If it’s RHOSP16, populate 'trilio_env_osp16.yaml' file with the triliovault container urls. Changes looks like following.

Update overcloud - This step will update the triliovault containers on overcloud

• Run your overcloud deploy command again. It will update the triliovault containers on overcloud.

• Command looks like following. \

[Optional] If you want to verify that triliovault got upgraded successfully, use following steps.

1. Verify triliovault datamover api container got updated on nova-api nodes

2. Verify triliovault datamover container got updated on nova-compute nodes

3. Verify triliovault horizon got updated on horizon nodes

Generic Pre-requisites

• Please ensure to complete the upgrade of all the TVault components on Openstack controller & compute nodes before starting the rolling upgrade of TVM.

• The mentioned gemfury repository should be accessible from TVault VM.

• Please ensure the following points before starting the upgrade process:

  • No snapshot OR restore to be running.

  • Global job-scheduler should be disabled.

• Take a backup of the conf files on all TVM nodes.

• Activate the virtual environment on all TVM nodes.

• Export new TVault version PYPI url:

Upgrade s3fuse/tvault-object-store

• Run the following command on all TVM nodes to upgrade s3fuse and its dependent packages.

Upgrade tvault-configurator

• Run the following command on all TVM nodes to upgrade tvault-configurator and its dependent packages.

Upgrade workloadmgr

• Run the upgrade command on all TVM nodes to upgrade workloadmgr and its dependent packages (workloadmgrclient, contegoclient, etc)

Updating Config Parameters of specific services

• Update wlm-cron service entries

  • If Reconfigure is NOT planned, please perform following steps on all TVM nodes, else skip.

    • Update the following two parameters in wlm-cron.service systemd file (/etc/systemd/system/wlm-cron.service) :
    • And once done, use the following command to reload the service file:
• Maria DB changes

  • If Reconfigure is planned

    • Remove Galera clustered-flag from all TVM nodes & proceed with reconfigure
  • If Reconfigure is NOT planned

    • Increase the max SQL connections limit by doing the following steps:

      • Edit /etc/my.cnf.d/server.cnf file on each TVM node

      • Add the parameter max_connections=5000 under [mysqld] section

      • Stop and Start MariaDB service on each node one by one

Post Upgrade Steps

• Restore the backed-up config files
• Restart following services on all node(s) using respective commands
• Enable Global Job Scheduler

• Restart pcs resources only on the primary node
• Verify the status of the services

  • Note: tvault-object-store will run only if TVault configured with S3 backend storage
• Additional check for wlm-cron on primary node
• Check the mount point using “df -h” command