# Upgrading on RHOSP ## 0] Pre-requisites Please ensure the following points are met before starting the upgrade process: * No Snapshot or Restore is running * Global job scheduler is disabled * wlm-cron is disabled on the Trilio Appliance #### Deactivating the wlm-cron service The following sets of commands will disable the wlm-cron service and verify that it is has been completly shut-down. ``` [root@TVM2 ~]# pcs resource disable wlm-cron [root@TVM2 ~]# systemctl status wlm-cron ● wlm-cron.service - workload's scheduler cron service Loaded: loaded (/etc/systemd/system/wlm-cron.service; disabled; vendor preset : disabled) Active: inactive (dead) Jun 11 08:27:06 TVM2 workloadmgr-cron[11115]: 11-06-2021 08:27:06 - INFO - 1...t Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: 140686268624368 Child 11389 ki...5 Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: 11-06-2021 08:27:07 - INFO - 1...5 Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: Shutting down thread pool Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: 11-06-2021 08:27:07 - INFO - S...l Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: Stopping the threads Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: 11-06-2021 08:27:07 - INFO - S...s Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: All threads are stopped succes...y Jun 11 08:27:07 TVM2 workloadmgr-cron[11115]: 11-06-2021 08:27:07 - INFO - A...y Jun 11 08:27:09 TVM2 systemd[1]: Stopped workload's scheduler cron service. Hint: Some lines were ellipsized, use -l to show in full. [root@TVM2 ~]# pcs resource show wlm-cron Resource: wlm-cron (class=systemd type=wlm-cron) Meta Attrs: target-role=Stopped Operations: monitor interval=30s on-fail=restart timeout=300s (wlm-cron-monito r-interval-30s) start interval=0s on-fail=restart timeout=300s (wlm-cron-start-int erval-0s) stop interval=0s timeout=300s (wlm-cron-stop-interval-0s) [root@TVM2 ~]# ps -ef | grep -i workloadmgr-cron root 15379 14383 0 08:27 pts/0 00:00:00 grep --color=auto -i workloadmgr -cron ``` ## 1.] \[On Undercloud node] Clone latest Trilio repository and upload Trilio puppet module {% hint style="warning" %} All commands need to be run as user 'stack' on undercloud node {% endhint %} {% hint style="warning" %} The Trilio appliance connected to this installation needs to be of version 4.1 HF10 {% endhint %} ### 1.1] Clone Trilio cfg scripts repository ``` cd /home/stack mv triliovault-cfg-scripts triliovault-cfg-scripts-old git clone -b hotfix-13-TVO/4.1 https://github.com/trilioData/triliovault-cfg-scripts.git cd triliovault-cfg-scripts/redhat-director-scripts// ``` Separate directories are created as per Redhat OpenStack release under 'triliovault-cfg-scripts/redhat-director-scripts/' directory. Use all scripts/templates from respective directory. For ex, if your RHOSP release is 13, then use scripts/templates from 'triliovault-cfg-scripts/redhat-director-scripts/rhosp13' directory only. {% hint style="info" %} Available RHOSP\_RELEASE\_\_\_DIRECTORY values are: rhosp13\ rhosp16.1\ rhosp16.2 {% endhint %} {% hint style="warning" %} **RHOSP 16.0** is not supported anymore as RedHat has officially stopped supporting it. However, Trilio maintained it for some time and stopped the support from 4.1HF11 onwards. The latest hotfix available for RHOSP16.0 is 41.HF10. Reach out to the Support team for any help. {% endhint %} ### 1.2] If backup target type is 'Ceph based S3' with SSL: 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 the puppet directory of the right release. ``` cp s3-cert.pem /home/stack/triliovault-cfg-scripts/redhat-director-scripts//puppet/trilio/files/ ``` ## 2] Upload Trilio puppet module ``` cd /home/stack/triliovault-cfg-scripts/redhat-director-scripts//scripts/ ./upload_puppet_module.sh ## Output of above command looks like following. Creating tarball... Tarball created. Creating heat environment file: /home/stack/.tripleo/environments/puppet-modules-url.yaml Uploading file to swift: /tmp/puppet-modules-8Qjya2X/puppet-modules.tar.gz +-----------------------+---------------------+----------------------------------+ | object                | container           | etag                             | +-----------------------+---------------------+----------------------------------+ | puppet-modules.tar.gz | overcloud-artifacts | 368951f6a4d39cfe53b5781797b133ad | +-----------------------+---------------------+----------------------------------+ ## Above command creates following file. ls -ll /home/stack/.tripleo/environments/puppet-modules-url.yaml ``` ## 3] Update overcloud roles data file to include Trilio services Trilio has two services as explained below.\ You need to add these two services to your roles\_data.yaml.\ If you do not have customized roles\_data file, you can find your default roles\_data.yaml file at `/usr/share/openstack-tripleo-heat-templates/roles_data.yaml` on undercloud. You need to find that role\_data file and edit it to add the following Trilio services. **i) Trilio Datamover Api Service:** Service Entry in roles\_data yaml: `OS::TripleO::Services::TrilioDatamoverApi` {% hint style="info" %} This service needs to be co-located with database and keystone services. That said, you need to add this service on the same role as of keystone and database service. {% endhint %} Typically this service should be deployed on controller nodes where keystone and database runs.\ If you are using RHOSP's pre-defined roles, you need to add`OS::TripleO::Services::TrilioDatamoverApi`service to `Controller role`. **ii) Trilio Datamover Service:**\ Service Entry in roles\_data yaml: `OS::TripleO::Services::TrilioDatamover`\ This service should be deployed on role where `nova-compute` service is running. If you are using RHOSP's pre-defined roles, you need to add our `OS::TripleO::Services::TrilioDatamover` service to `Compute role`. If you have defined your custom roles, then you need to identify the role name where in 'nova-compute' service is running and then you need to add 'OS::TripleO::Services::TrilioDatamover' service to that role. ## 4] Prepare latest Trilio container images {% hint style="warning" %} All commands need to be run as user 'stack' {% endhint %} {% hint style="info" %} Refer to the word **\** as ***4.1.94-hotfix-16** in the below sections* {% endhint %} Trilio containers are pushed to 'RedHat Container Registry'. Registry URL is '[registry.connect.redhat.com](http://registry.connect.redhat.com/)'.\ The Trilio container URLs are as follows: ### 4.1] available container images #### RHOSP 13 ``` Trilio Datamove container: registry.connect.redhat.com/trilio/trilio-datamover:-rhosp13 Trilio Datamover Api Container: registry.connect.redhat.com/trilio/trilio-datamover-api:-rhosp13 Trilio horizon plugin: registry.connect.redhat.com/trilio/trilio-horizon-plugin:-rhosp13 ``` #### RHOSP 16.1 ``` Trilio Datamover container: registry.connect.redhat.com/trilio/trilio-datamover:-rhosp16.1 Trilio Datamover Api Container: registry.connect.redhat.com/trilio/trilio-datamover-api:-rhosp16.1 Trilio horizon plugin: registry.connect.redhat.com/trilio/trilio-horizon-plugin:-rhosp16.1 ``` #### RHOSP 16.2 ``` Trilio Datamover container: registry.connect.redhat.com/trilio/trilio-datamover:-rhosp16.2 Trilio Datamover Api Container: registry.connect.redhat.com/trilio/trilio-datamover-api:-rhosp16.2 Trilio horizon plugin: registry.connect.redhat.com/trilio/trilio-horizon-plugin:-rhosp16.2 ``` There are three registry methods available in RedHat OpenStack Platform. 1. Remote Registry 2. Local Registry 3. Satellite Server ### 4.2] Remote Registry {% hint style="info" %} Please refer to the [following overview](#4-1-available-container-images) to see which containers are available. {% endhint %} Follow this section when 'Remote Registry' is used. For this method, it is not necessary to pull the containers in advance.\ It is only necessary to populate the trilio\_env.yaml file with the Trilio container URLs from Redhat registry. Populate the trilio\_env.yaml with container URLs for: * Trilio Datamover container * Trilio Datamover api container * Trilio Horizon Plugin {% hint style="info" %} trilio\_env.yaml will be available in\ \_\_`triliovault-cfg-scripts/redhat-director-scripts//environments` {% endhint %} #### Example ``` # For RHOSP13 $ grep 'Image' trilio_env.yaml DockerTrilioDatamoverImage: registry.connect.redhat.com/trilio/trilio-datamover:-rhosp13 DockerTrilioDmApiImage: registry.connect.redhat.com/trilio/trilio-datamover-api:-rhosp13 DockerHorizonImage: registry.connect.redhat.com/trilio/trilio-horizon-plugin:-rhosp13 # For RHOSP16.1 $ grep 'Image' trilio_env.yaml DockerTrilioDatamoverImage: registry.connect.redhat.com/trilio/trilio-datamover:-rhosp16.1 DockerTrilioDmApiImage: registry.connect.redhat.com/trilio/trilio-datamover-api:-rhosp16.1 ContainerHorizonImage: registry.connect.redhat.com/trilio/trilio-horizon-plugin:-rhosp16.1 # For RHOSP16.2 $ grep 'Image' trilio_env.yaml DockerTrilioDatamoverImage: registry.connect.redhat.com/trilio/trilio-datamover:-rhosp16.2 DockerTrilioDmApiImage: registry.connect.redhat.com/trilio/trilio-datamover-api:-rhosp16.2 ContainerHorizonImage: registry.connect.redhat.com/trilio/trilio-horizon-plugin:-rhosp16.2 ``` ### 4.2] Local Registry {% hint style="info" %} Please refer to the [this overview](#4-1-available-container-images) to see which containers are available. {% endhint %} Follow this section when 'local registry' is used on the undercloud. In this case it is necessary to push the Trilio containers to the undercloud registry.\ Trilio provides shell scripts which will pull the containers from 'registry.connect.redhat.com' and push them to the undercloud and updates the trilio\_env.yaml. #### RHOSP13 ``` cd /home/stack/triliovault-cfg-scripts/redhat-director-scripts/rhosp13/scripts/ ./prepare_trilio_images.sh -rhosp13 ``` Verify the changes ``` $ grep 'Image' ../environments/trilio_env.yaml DockerTrilioDatamoverImage: 172.25.2.2:8787/trilio/trilio-datamover:-rhosp13 DockerTrilioDmApiImage: 172.25.2.2:8787/trilio/trilio-datamover-api:-rhosp13 DockerHorizonImage: 172.25.2.2:8787/trilio/trilio-horizon-plugin:-rhosp13 ``` #### RHOSP16.1 ``` cd /home/stack/triliovault-cfg-scripts/redhat-director-scripts/rhosp16.1/scripts/ sudo ./prepare_trilio_images.sh -rhosp16.1 ``` Verify the changes: ``` $ grep 'Image' ../environments/trilio_env.yaml DockerTrilioDatamoverImage: undercloud.ctlplane.localdomain:8787/trilio/trilio-datamover:-rhosp16.1 DockerTrilioDmApiImage: undercloud.ctlplane.localdomain:8787/trilio/trilio-datamover-api:-rhosp16.1 ContainerHorizonImage: undercloud.ctlplane.localdomain:8787/trilio/trilio-horizon-plugin:-rhosp16.1 ``` #### RHOSP16.2 ``` cd /home/stack/triliovault-cfg-scripts/redhat-director-scripts/rhosp16.2/scripts/ sudo ./prepare_trilio_images.sh -rhosp16.2 ``` Verify the changes ``` $ grep 'Image' ../environments/trilio_env.yaml DockerTrilioDatamoverImage: undercloud.ctlplane.localdomain:8787/trilio/trilio-datamover:-rhosp16.2 DockerTrilioDmApiImage: undercloud.ctlplane.localdomain:8787/trilio/trilio-datamover-api:-rhosp16.2 ContainerHorizonImage: undercloud.ctlplane.localdomain:8787/trilio/trilio-horizon-plugin:-rhosp16.2 ``` The changes can be verified using the following commands. ``` (undercloud) [stack@undercloud redhat-director-scripts/]$ openstack tripleo container image list | grep trilio | docker://undercloud.ctlplane.localdomain:8787/trilio/trilio-datamover:-rhosp16.1 | | | docker://undercloud.ctlplane.localdomain:8787/trilio/trilio-datamover-api:-rhosp16.1 | | | docker://undercloud.ctlplane.localdomain:8787/trilio/trilio-horizon-plugin:-rhosp16.1 | ----------------------------------------------------------------------------------------------------- (undercloud) [stack@undercloud redhat-director-scripts]$ grep 'Image' ../environments/trilio_env.yaml DockerTrilioDatamoverImage: undercloud.ctlplane.localdomain:8787/trilio/trilio-datamover:-rhosp16.1 DockerTrilioDmApiImage: undercloud.ctlplane.localdomain:8787/trilio/trilio-datamover-api:-rhosp16.1 ContainerHorizonImage: undercloud.ctlplane.localdomain:8787/trilio/trilio-horizon-plugin:-rhosp16.1 ``` ### 4.3] Red Hat Satellite Server {% hint style="info" %} Please refer to the [following overview](#4-1-available-container-images) to see which containers are available. {% endhint %} Follow this section when a Satellite Server is used for the container registry. Pull the Trilio containers on the Red Hat Satellite using the given [Red Hat registry URLs.](/openstack/tvo-4.1/deployment/configuring-and-installing-triliovault/installing-on-rhosp.md#prepare-for-deployment) Populate the trilio\_env.yaml with container urls. #### RHOSP 13 ``` $ grep 'Image' ../environments/trilio_env.yaml DockerTrilioDatamoverImage: /trilio/trilio-datamover:-rhosp13 DockerTrilioDmApiImage: /trilio/trilio-datamover-api:-rhosp13 DockerHorizonImage: /trilio/trilio-horizon-plugin:-rhosp13 ``` #### RHOSP16.1 ``` $ grep 'Image' trilio_env.yaml DockerTrilioDatamoverImage: /trilio/trilio-datamover:-rhosp16.1 DockerTrilioDmApiImage: /trilio/trilio-datamover-api:-rhosp16.1 ContainerHorizonImage: /trilio/trilio-horizon-plugin:-rhosp16.1 ``` #### RHOSP16.2 ``` $ grep 'Image' trilio_env.yaml DockerTrilioDatamoverImage: /trilio/trilio-datamover:-rhosp16.2 DockerTrilioDmApiImage: /trilio/trilio-datamover-api:-rhosp16.2 ContainerHorizonImage: /trilio/trilio-horizon-plugin:-rhosp16.2 ``` ## 5. Verify Trilio environment details It is recommended to re-populate the backup target details in the freshly downloaded trilio\_env.yaml file.\ This will ensure that parameters that have been added since the last update/installation of Trilio are available and will be filled out too. Locations of the trilio\_env.yaml: ``` RHOSP13: /home/stack/triliovault-cfg-scripts/redhat-director-scripts/rhosp13/environments/trilio_env.yaml RHOSP16.1: /home/stack/triliovault-cfg-scripts/redhat-director-scripts/rhosp16.1/environments/trilio_env.yaml RHOSP16.2: /home/stack/triliovault-cfg-scripts/redhat-director-scripts/rhosp16.2/environments/trilio_env.yaml ``` For more details about the trilio\_env.yaml please check [here](/openstack/tvo-4.1/deployment/configuring-and-installing-triliovault/installing-on-rhosp.md#5-provide-environment-details-in-trilio-env-yaml). ## 6] Update Overcloud Trilio components Use the following heat environment file and roles data file in overcloud deploy command: 1. `trilio_env.yaml` 2. `roles_data.yaml` 3. Use correct Trilio endpoint map file as per available Keystone endpoint configuration 1. Instead of `tls-endpoints-public-dns.yaml` file, use `environments/trilio_env_tls_endpoints_public_dns.yaml` 2. Instead of `tls-endpoints-public-ip.yaml` file, use`environments/trilio_env_tls_endpoints_public_ip.yaml` 3. Instead of `tls-everywhere-endpoints-dns.yaml` file, use`environments/trilio_env_tls_everywhere_dns.yaml` To include new environment files use '-e' option and for roles data file use '-r' option.\ An example overcloud deploy command is shown below: ``` openstack overcloud deploy --templates \ -e /home/stack/templates/node-info.yaml \ -e /home/stack/templates/overcloud_images.yaml \ -e /home/stack/triliovault-cfg-scripts/redhat-director-scripts//environments/trilio_env.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/enable-tls.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/inject-trust-anchor.yaml \ -e /home/stack/triliovault-cfg-scripts/redhat-director-scripts//environments/trilio_env_tls_endpoints_public_dns.yaml \ --ntp-server 192.168.1.34 \ --libvirt-type qemu \ --log-file overcloud_deploy.log \ -r /usr/share/openstack-tripleo-heat-templates/roles_data.yaml ``` ## 7] Verify deployment {% hint style="danger" %} If the containers are in restarting state or not listed by the following command then your deployment is not done correctly. Please recheck if you followed the complete documentation. {% endhint %} ### 7.1] On Controller node Make sure Trilio dmapi and horizon containers are in a running state and no other Trilio container is deployed on controller nodes.\ When the role for these containers is not "controller" check on respective nodes according to configured roles\_data.yaml. ``` [root@overcloud-controller-0 heat-admin]# podman ps | grep trilio 26fcb9194566 rhosptrainqa.ctlplane.localdomain:8787/trilio/trilio-datamover-api:-rhosp16.1 kolla_start 5 days ago Up 5 days ago trilio_dmapi 094971d0f5a9 rhosptrainqa.ctlplane.localdomain:8787/trilio/trilio-horizon-plugin:-rhosp16.1 kolla_start 5 days ago Up 5 days ago horizon ``` ### 7.2] On Compute node Make sure Trilio datamover container is in running state and no other Trilio container is deployed on compute nodes. ``` [root@overcloud-novacompute-0 heat-admin]# podman ps | grep trilio b1840444cc59 rhosptrainqa.ctlplane.localdomain:8787/trilio/trilio-datamover:-rhosp16.1 kolla_start 5 days ago Up 5 days ago trilio_datamover ``` ### 7.3] On the node with Horizon service Make sure horizon container is in running state. Please note that 'Horizon' container is replaced with Trilio Horizon container. This container will have latest OpenStack horizon + Trilio's horizon plugin. ``` [root@overcloud-controller-0 heat-admin]# podman ps | grep horizon 094971d0f5a9 rhosptrainqa.ctlplane.localdomain:8787/trilio/trilio-horizon-plugin:-rhosp16.1 kolla_start 5 days ago Up 5 days ago horizon ``` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.trilio.io/openstack/tvo-4.1/deployment/upgrade-triliovault/upgrading-on-rhosp.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.