Trilio has four main software components:
  1. 1.
    Trilio ships as a QCOW2 image. User can instantiate one or more VMs from the QCOW2 image on a standalone KVM boxes.
  2. 2.
    Trilio API is a python module that is an extension to nova api service. This module is installed on all OpenStack controller nodes
  3. 3.
    Trilio Datamover is a python module that is installed on every OpenStack compute nodes
  4. 4.
    Trilio horizon plugin is installed as an add on to horizon servers. This module is installed on every server that runs horizon service.

System requirements Trilio Appliance

The Trilio Appliance is not supported as instance inside Openstack.
The Trilio Appliance gets delivered as a qcow2 image, which gets attached to a virtual machine.
Trilio supports KVM-based hypervisors on x86 architectures, with the following properties:
2.0.0 and above
2.0.0 and above
2.6.0 and above
The recommended size of the VM for the Trilio Appliance is:
When running Trilio in production, a 3-node cluster of the Trilio appliance is recommended for high availability and load balancing.
24 GB
The qcow2 image itself defines the 40GB disk size of the VM.
In the rare case of the Trilio Appliance database or log files getting larger than 40GB disk, contact or open a ticket with Trilio Customer Success to attach another drive to the Trilio Appliance.

Software Requirements

In addition to the Trilio Appliance does Trilio contain components, which are installed directly into the Openstack itself.
Each Openstack distribution comes with a set of supported operating systems. Please check the support matrix to see, which Openstack Distribution is supported with which Operating System.
Additionally, it is necessary to have the nfs-common packages installed on the compute nodes in case of using the NFS protocol for the backup target.

OpenStack Barbican for encryption

Since Trilio for OpenStack 4.2 is T4O capable of providing encrypted backups
The Trilio for OpenStack solution is leveraging the OpenStack Barbican service to provide encryption capabilities for its backups.
To be precise, T4O is using secrets provided by Barbican to encrypt and decrypt backups. Barbican is therefore required to utilize this feature.