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
  • Import workloads
  • Orphaned Workloads
  • Reassigning Workloads

Was this helpful?

Export as PDF
  1. Admin Guide

Workload Import & Migration

PreviousManaging TrustsNextDisaster Recovery

Last updated 7 months ago

Was this helpful?

Each Trilio Workload has a dedicated owner. The ownership of a Workload is defined by:

  • Openstack User - The Openstack User-ID is assigned to a Workload

  • Openstack Project - The Openstack Project-ID is assigned to a Workload

  • Openstack Cloud - The Trilio Serviceuser-ID is assigned to a Workload

Openstack Users can update the User ownership of a Workload by modifying the Workload.

This ownership secures, that only the owners of a Workload are able to work with it.

Openstack Administrators can reassign Workloads or reimport Workloads from older Trilio installations.

Import workloads

Workload import allows to import Workloads existing on the Backup Target into the Trilio database.

The Workload import is designed to import Workloads, which are owned by the Cloud.

It will not import or list any Workloads that are owned by a different cloud.

To get a list of importable Workloads use the following CLI command:

workloadmgr workload-get-importworkloads-list [--project_id <project_id>]
  • --project_id <project_id> List workloads belongs to given project only.

To import Workloads into the Trilio database use the following CLI command:

workloadmgr workload-importworkloads [--workloadids <workloadid>]
  • --workloadids <workloadid> Specify workload ids to import only specified workloads. Repeat option for multiple workloads.

Orphaned Workloads

The definition of an orphaned Workload is from the perspective of a specific Trilio installation. Any workload that is located on the Backup Target Storage, but not known to the TrilioVualt installation is considered orphaned.

Further is to divide between Workloads that were previously owned by Projects/Users in the same cloud or are migrated from a different cloud.

The following CLI command provides the list of orphaned workloads:

workloadmgr workload-get-orphaned-workloads-list [--migrate_cloud {True,False}]
                                                 [--generate_yaml {True,False}]

Running this command against a Backup Target with many Workloads can take a bit of time. Trilio is reading the complete Storage and verifies every found Workload against the Workloads known in the database.

Reassigning Workloads

Openstack administrators are able to reassign a Workload to a new owner. This involves the possibility to migrate a Workload from one cloud to another or between projects.

Reassigning a workload only changes the database of the target Trilio installation. When the Workload was managed before by a different Trilio installation, will that installation not be updated.

Use the following CLI command to reassign a Workload:

workloadmgr workload-reassign-workloads
                                        [--old_tenant_ids <old_tenant_id>]
                                        [--new_tenant_id <new_tenant_id>]
                                        [--workload_ids <workload_id>]
                                        [--user_id <user_id>]
                                        [--migrate_cloud {True,False}]
                                        [--map_file <map_file>]

A sample mapping file with explanations is shown below:

reassign_mappings:
   - old_tenant_ids: [] #user can provide list of old_tenant_ids or workload_ids
     new_tenant_id: new_tenant_id
     user_id: user_id
     workload_ids: [] #user can provide list of old_tenant_ids or workload_ids
     migrate_cloud: True/False #Set to True if want to reassign workloads from
                  # other clouds as well. Default is False

   - old_tenant_ids: [] #user can provide list of old_tenant_ids or workload_ids
     new_tenant_id: new_tenant_id
     user_id: user_id
     workload_ids: [] #user can provide list of old_tenant_ids or workload_ids
     migrate_cloud: True/False #Set to True if want to reassign workloads from
                  # other clouds as well. Default is False

--migrate_cloud {True,False} Set to True if you want to list workloads from other clouds as well. Default is False.

--generate_yaml {True,False} Set to True if want to generate output file in yaml format, which would be further used as input for workload reassign API.

--old_tenant_ids <old_tenant_id> Specify old tenant ids from which workloads need to reassign to new tenant. Specify multiple times to choose Workloads from multiple tenants.

--new_tenant_id <new_tenant_id> Specify new tenant id to which workloads need to reassign from old tenant. Only one target tenant can be specified.

--workload_ids <workload_id> Specify workload_ids which need to reassign to new tenant. If not provided then all the workloads from old tenant will get reassigned to new tenant. Specifiy multiple times for multiple workloads.

--user_id <user_id> Specify user id to which workloads need to reassign from old tenant. only one target user can be specified.

--migrate_cloud {True,False} Set to True if want to reassign workloads from other clouds as well. Default if False

--map_file Provide file path(relative or absolute) including file name of reassign map file. Provide list of old workloads mapped to new tenants. Format for this file is YAML.

➡️
➡️
➡️
➡️
➡️
➡️
➡️
➡️
➡️
➡️