Cloud-Native and Containerized

T4O represents a comprehensively containerized deployment model, eliminating the necessity for any KVM-based appliances for service deployment. This marks a departure from earlier T4O releases, where such appliances were required.

Summary of Requirements

Trilio requires its containers to be deployed on the same plane as OpenStack, utilizing existing cluster resources.

As described in the architecture overview, Trilio requires sufficient cluster resources to deploy its components on both the Controller Plane and Compute Planes.

  1. Valid Trilio License & Acceptance of the EULA

  2. Sufficient resources available on the target OpenShift cluster nodes

  3. Sufficient storage capacity and connectivity on Cinder for snapshotting operations

  4. Sufficient network capabilities for efficient data transfer of workloads

  5. User and Role permissions for access to required cluster objects

  6. Optional features may have specific requirements such as encryption, file search, snapshot mount, FRM instance, etc

  7. Set hw_qemu_guest_agent=True property on the image and install qemu-guest-agent on the VM, in order to avoid any file system inconsistencies post restore.

  8. For the VMware to OpenStack migration feature, please refer to the prerequisite and limitations pages.

pageNetwork ConsiderationspageInstallation Strategy and Preparation

Last updated