RHOSP Upgrade

Clone updated triliovault-cfg-scripts github repo

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

  • Clone updated repo\

    cd /home/stack
mv triliovault-cfg-scripts triliovault-cfg-scripts-old
git clone -b v4.0maintenance https://github.com/trilioData/triliovault-cfg-scripts.git
cd triliovault-cfg-scripts/redhat-director-scripts/

  • 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'

## If it's RHOSP13
cp s3-cert.pem /home/stack/triliovault-cfg-scripts/redhat-director-scripts/puppet/trilio/files/

## If it's RHOSP16
cp s3-cert.pem /home/stack/triliovault-cfg-scripts/redhat-director-scripts/puppet5/trilio/files/

  • Upload triliovault puppet module

## If it's RHOSP13
./upload_puppet_module.sh

## If it's RHOSP16
./upload_puppet_module_puppet5.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

  • Copy old trilio env file to new repository

Pull latest triliovault container images and update triliovault environment yaml file

Trilio containers are pushed to 'RedHat Container Registry'. Registry URL is 'registry.connect.redhat.com'. Following are the triliovault container pull urls.

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

PreviousCentOS/RHEL based Openstack environmentsNextUpgrade Trilio Appliance

Last updated

Was this helpful?