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
- If it's RHOSP13, copy 'trilio_env.yaml
cp /home/stack/triliovault-cfg-scripts-old/redhat-director-scripts/trilio_env.yaml .
- If it's RHOSP16 the copy 'trilio_env_osp16.yaml'
cp /home/stack/triliovault-cfg-scripts-old/redhat-director-scripts/trilio_env_osp16.yaml .
Trilio containers are pushed to 'RedHat Container Registry'. Registry URL is 'registry.connect.redhat.com'.
Following are the triliovault container pull urls.
Note: '4.0.115' is Trilio 4.0 build version. Container tag: 4.0.115-rhosp16
There are three registry methods available in RedHat Openstack Platform.
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.\
## Update trilio_env.yaml with latest triliovault image urls. Changes should look like following.
$ grep 'Image' trilio_env.yaml
DockerTrilioDatamoverImage: registry.connect.redhat.com/trilio/trilio-datamover:4.0.115-rhosp13
DockerTrilioDmApiImage: registry.connect.redhat.com/trilio/trilio-datamover-api:4.0.115-rhosp13
## In overcloud_images.yaml which has RHOSP container details (Generally we keep this file at /home/stack/templates/overcloud_images.yaml),
## replace 'DockerHorizonImage:...' entry with following entry(Trilio horizon container url). This will make sure Trilio's dashboard gets deployed on OpenStack Horizon.
DockerHorizonImage: registry.connect.redhat.com/trilio/trilio-horizon-plugin:4.0.115-rhosp13
## Make sure that changes are made with following command and expected output.
$ grep 'trilio' /home/stack/templates/overcloud_images.yaml
DockerHorizonImage: registry.connect.redhat.com/trilio/trilio-horizon-plugin:4.0.115-rhosp13
If it’s RHOSP16, populate 'trilio_env_osp16.yaml' file with triliovault container urls.
Changes looks like following.\
If it’s RHOS16, run following script. Script, pulls the triliovault containers and updates the triliovault environment file with urls.\
sudo ./podman_prepare_images.sh <UNDERCLOUD_REGISTRY_HOSTNAME> <CONTAINER_TAG>
## Example
sudo ./podman_prepare_images.sh trilio-undercloud.ctlplane.localdomain 4.0.115-rhosp16
## 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.
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.
