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
  • Definition
  • Creation
  • Update and Changes
  • Discover VMs
  • Deletion

Was this helpful?

Export as PDF
  1. User Guide
  2. VMware migration

Migration Plans

Definition

A Migration Plan is a structured and pre-defined set of instructions that outlines the process and details for migrating Virtual Machines (VMs) from a VMware environment to OpenStack. It serves as a blueprint for orchestrating the migration, including the selection of VMs, and managing the overall migration workflow. Each plan may have a name and may include a description to provide additional context and easy identification. Migration Plans are created and managed by users to ensure a systematic and controlled migration process.

Creation

To initiate the migration process, users must create a Migration Plan:

  • Provide a name and description for the plan.

  • Select VMs from the list of VMware VMs. This list does not include the VMs which are already part of a Migration Plan.

Update and Changes

Any modification to the plan requires users to:

  • Revisit the plan details for updates.

  • Execute the "Discover VMs" call to fetch and update resource information in the Trilio service DB.

Failure to perform a "Discover VMs" after plan modification can lead to unexpected outcomes.

Discover VMs

Discover VMs is an operation within the migration process that involves querying and collecting resource information from VMware for the VMs included in a Migration Plan. This operation is crucial for maintaining up-to-date details about the VMs, such as configuration, networking, and storage.

After creating or modifying a Migration Plan, users must:

  • Trigger the "Discover VMs" operation.

  • This operation collects resource information of VMs in the plan from VMware and stores it in the WLM service DB.

  • "Discover VMs" must be called every time the plan is updated to ensure accurate information for migration. It ensures accuracy in subsequent migration steps and helps prevent unexpected outcomes due to outdated information.

Deletion

The user can also delete a Migration Plan if required. But it will need all the initiated migrations to be deleted. Refer to this page for deleting the initiated migrations for more information.

How-to Guide: Creating a Migration Plan

PreviousVMware migrationNextHow-to Guide: Creating a Migration Plan

Last updated 1 year ago

Was this helpful?