LogoLogo
T4O-5.x
T4O-5.x
  • About Trilio for OpenStack
    • Welcome to Trilio for OpenStack
    • T4O Architecture
    • Release Notes
    • Compatibility Matrix
    • Resources
      • 5.2.4
      • 5.2.3
      • 5.2.2
      • 5.2.1
      • 5.2.0
      • 5.1.0
      • 5.0.0
  • Getting Started
    • Requirements
      • Network Considerations
      • Installation Strategy and Preparation
    • Getting started with Trilio on Red-Hat OpenStack Platform (RHOSP)
      • Post Installation Health-Check
    • Getting started with Trilio on Kolla-Ansible OpenStack
    • Getting started with Trilio on Canonical OpenStack
    • Software Driven Migration: VMware to OpenStack
      • Trilio's Approach
      • Supported Environments
      • Preparations
      • Deployment & Configuration
      • VM Migration Tool
      • Limitations
    • Licensing
    • Installing WorkloadManager CLI client
    • Uninstall Trilio
      • Uninstalling from RHOSP
  • Upgrading to T4O-5.x from older supported versions
    • Supported Trilio Upgrade Path
    • Upgrading on RHOSP
    • Upgrading on Kolla
    • Enabling T4O 4.1 or older backups when using NFS backup target
  • Advanced Configuration
    • Switching NFS Backing file
    • Multi-IP NFS Backup target mapping file configuration
    • Advanced Ceph configurations
      • Additions for multiple CEPH configurations
    • Multi-Region Deployments
  • User Guide
    • Workloads
    • Snapshots
    • Restores
    • File Search
    • Snapshot Mount
    • Schedulers
    • E-Mail Notifications
    • VMware migration
      • Migration Plans
        • How-to Guide: Creating a Migration Plan
      • Migrations
        • How-to Guide: Initiating a Migration
  • Admin Guide
    • Backups-Admin Area
    • Workload Policies
    • Workload Quotas
    • Managing Trusts
    • Workload Import & Migration
    • Disaster Recovery
      • Example runbook for Disaster Recovery using NFS
      • Example runbook for Disaster Recovery using S3
    • Migrating encrypted Workloads
    • Rebasing existing workloads
  • Troubleshooting
    • Frequently Asked Questions
    • General Troubleshooting Tips
    • Important log files
  • API GUIDE
    • Workloads
    • Snapshots
    • Restores
    • File Search
    • Snapshot Mount
    • Schedulers
    • E-Mail Notification Settings
    • Workload Policies
    • Workload Quotas
    • Managing Trusts
    • Workload Import and Migration
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Getting Started

Requirements

Previous5.0.0NextNetwork Considerations

Last updated 1 year ago

Was this helpful?

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 , Trilio requires sufficient cluster resources to deploy its components on both the Controller Plane and Compute Planes.

  1. Valid Trilio License & Acceptance of the

  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 and pages.

architecture overview
EULA
prerequisite
limitations
Network Considerations
Installation Strategy and Preparation