Getting started with Trilio on Canonical OpenStack
PreviousGetting started with Trilio on Kolla-Ansible OpenStackNextSoftware Driven Migration: VMware to OpenStack
Last updated
Last updated
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.
Canonical OpenStack doesn't require the Trilio Cluster. The required services are installed and managed via JuJu Charms.
A Canonical OpenStack base setup deployed for a required release like Jammy Antelope/Bobcat. Refer Compatibility Matrix
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).
If trilio-wlm service is assigned to any nova-compute node then wlm mysql router service fails to start. Hence, please ensure to assign trilio-wlm service to some other node.
Sample Trilio overlay bundles (T4O release wise) can be found at LINK
Alternatively, triliovault-cfg-scripts repository can be cloned to get the sample overlay bundles.
Value of trilio_branch can be taken from release specific Resources
Following table provides the details of various values to be updated in overlay bundle.
For the AWS S3 storage backend, we need to use `http://s3.amazonaws.com` as S3 end-point URL.
3.1] Do a dry run to check if the Trilio bundle is working
3.2] Trigger deployment
3.3] Wait until all the Trilio units are deployed successfully. Check the status via juju status command.
4.1] Once the deployment is complete, perform the below operations:
a. Create cloud admin trust & add licence
Note: Reach out to the Trilio support team for the license file.
5.1] After T4O deployment steps are over, it can take sometime for all units to get deployed successfully. Deployment is considered successful when all the units show Unit is Ready in the message column.
To verify the same, following command (& sample output) can be used to fetch the Trilio units/applications.
6.1] To debug any specific unit : juju debug-log --include <UNIT_NAME_IN_ERROR>
Eg. If trilio-wlm/6 unit is in 'error' state, it's logs can be fetched using following command. Specific correct unit number from respective deployment using juju status command.
juju debug log --include trilio-wlm/6
For multipath enabled environments, perform the following actions
log into each nova compute node
add uxsock_timeout with value as 60000 (i.e. 60 sec) in /etc/multipath.conf
restart tvault-contego service
Charm names
Channel
Supported releases
latest/stable
Jammy (Ubuntu 22.04)
latest/stable
Jammy (Ubuntu 22.04)
latest/stable
Jammy (Ubuntu 22.04)
latest/stable
Jammy (Ubuntu 22.04)
Parameters
Summary
triliovault-pkg-source
Trilio debian package repo url; Refer release specific Resources page
machines
List of Machines available on canonical openstack setup
channel
Channel name as provided in release specific Resources page
revision
Latest values as provided by Trilio. Refer release specific Resources page
If Backup Target is NFS
nfs-shares
NFS server IP and share path
nfs-options
Options as per respective NFS server
If Backup Target is S3
tv-s3-endpoint-url
S3 Endpoint URL
tv-s3-secret-key
S3 Secret Key
tv-s3-access-key
S3 Access Key
tv-s3-region-name
S3 Region
tv-s3-bucket
S3 bucket
tv-s3-ssl
Set true for SSL enabled S3 endpoint URL
tv-s3-ssl-verify
Set true for SSL enabled S3 endpoint URL
tv-s3-ssl-cert
Required if S3 SSL/TLS certificates are self signed, else the parameter to be omitted. Provide path of the respective certificate file (.pem) from S3 in format tv-s3-ssl-cert: include-base64://<path_to_ca_cert>