Installing on Canonical OpenStack

Trilio and Canonical have started a partnership to ensure a native deployment of Trilio using JuJu Charms.

Those JuJu Charms are publicly available as Open Source Charms.

Trilio is providing the JuJu Charms to deploy Trilio 4.2 in Canonical OpenStack from Yoga release onwards only. JuJu Charms to deploy Trilio 4.2 in Canonical OpenStack up to wallaby release are developed and maintained by Canonical.

Canonical OpenStack doesn't require the Trilio Cluster. The required services are installed and managed via JuJu Charms.

The documentation of the charms can be found here:

TrilioVault data protection — charm-guide 0.0.1.dev818 documentationdocs.openstack.org

Juju charms for OpenStack Yoga release onwards

Charm names	Channel	Supported releases
trilio-charmers-trilio-wlm-jammy	latest/edge	Jammy (Ubuntu 22.04)
trilio-charmers-trilio-dm-api-jammy	latest/edge	Jammy (Ubuntu 22.04)
trilio-charmers-trilio-data-mover-jammy	latest/edge	Jammy (Ubuntu 22.04)
trilio-charmers-trilio-horizon-plugin-jammy	latest/edge	Jammy (Ubuntu 22.04)
trilio-charmers-trilio-wlm-focal	latest/edge	Focal (Ubuntu 20.04)
trilio-charmers-trilio-dm-api-focal	latest/edge	Focal (Ubuntu 20.04)
trilio-charmers-trilio-data-mover-focal	latest/edge	Focal (Ubuntu 20.04)
trilio-charmers-trilio-horizon-plugin-focal	latest/edge	Focal (Ubuntu 20.04)

Juju charms for other supported OpenStack releases upto wallaby

Charm names	Channel	Supported releases
trilio-wlm	4.2/stable	Focal (Ubuntu 20.04), Bionic (Ubuntu 18.04)
trilio-data-mover	4.2/stable	Focal (Ubuntu 20.04), Bionic (Ubuntu 18.04)
trilio-dm-api	4.2/stable	Focal (Ubuntu 20.04), Bionic (Ubuntu 18.04)
trilio-horizon-plugin	4.2/stable	Focal (Ubuntu 20.04), Bionic (Ubuntu 18.04)

Prerequisite

Have a canonical OpenStack base setup deployed for a required release like Jammy Zed/Yoga, Focal yoga/Wallaby/Victoria/Ussuri, or Bionic Ussuri/Queens.

Steps to install the Trilio charms

1. Export the OpenStack base bundle

juju export-bundle --filename openstack_base_file.yaml

2. Create a Trilio overlay bundle as per the OpenStack setup release using the charms given above.

Some sample Trilio overlay bundles can be found here.

NFS options for Cohesity NFS : nolock,soft,timeo=600,intr,lookupcache=none,nfsvers=3,retrans=10

Trilio File Search functionality requires that the Trilio Workload manager (trilio-wlm) be deployed as a virtual machine. File Search will not function if the Trilio Workload manager (trilio-wlm) is running as a lxd container(s).

3. If file search functionality is required, provision any additional node(s) that will be required for deploying the Trilio Workload manager (trilio-wlm) as a VM instead of lxd container(s).

4. Commission the additional node from MAAS UI.

5. Do a dry run to check if the Trilio bundle is working

juju deploy --dry-run ./openstack_base_file.yaml --overlay <Trilio bundle path>

6. Do the deployment

juju deploy ./openstack_base_file.yaml --overlay <Trilio bundle path>

7. Wait till all the Trilio units are deployed successfully. Check the status via juju status command.

8. Once the deployment is complete, perform the below operations:

1. Create cloud admin trust

Juju 2.x

juju run-action --wait trilio-wlm/leader create-cloud-admin-trust password=<openstack admin password>

Juju 3.x

juju run --wait trilio-wlm/leader create-cloud-admin-trust password=<openstack admin password>

1. Add license

juju attach-resource trilio-wlm license=<Path to trilio license file>

Juju 2.x

juju run-action --wait trilio-wlm/leader create-license

Juju 3.x

juju run --wait trilio-wlm/leader create-license

Note: Reach out to the Trilio support team for the license file.

For multipath enabled environments, perform the following actions

1. log into each nova compute node

2. add uxsock_timeout with value as 60000 (i.e. 60 sec) in /etc/multipath.conf

3. restart tvault-contego service

Sample Trilio overlay bundles

For bionic-queens openstack-origin parameter value for trilio-dm-api charm must be cloud:bionic-train

For the AWS S3 storage backend, we need to use `http://s3.amazonaws.com` as S3 end-point URL.

A few Sample overlay bundles for different OpenStack versions can be found HERE.