Migration refers to the process of transferring Virtual Machines and their associated resources from a VMware environment to an OpenStack environment. It involves multiple steps, including planning (creating a Migration Plan), discovery (fetching VM resource information), and the actual migration execution. During migration, users provide details such as migration name, and description, select VMs, map networks, map volume types, and configure specific parameters for each VM. The goal is to seamlessly move VM workloads while preserving their configurations and ensuring compatibility with the target OpenStack environment. Successful migration results in VMs running efficiently within the OpenStack infrastructure.
Check the prerequisites before initiating the migrations.
Once the VMs of the Migration Plan are discovered ( Discover VMs ), the user can initiate the migration.
Trilio provides 3 types of migrations and the user can choose as per their need, more details can be found here.
Dry-run Migration:
Create VMs on OpenStack with attached storage volumes, networking, and security groups for testing purposes while migrating the VM snapshot data from VMware.
Cold Migration:
Shut down VMware virtual machines and then migrate them to OpenStack. This process can take minutes to hours and may cause significant downtime, making it more disruptive.
Warm Migration:
Leverage VMware snapshots and the Change Block Tracking feature to migrate VMs with minimal disruption. Take snapshots, copy changed blocks, and then repeat the process after shutting down the VMs. The downtime can be significantly lower than that of a Cold Migration.
While initiating the migration, the user needs to provide a few more below-mentioned information to ensure a seamless migration of the VMs.
To perform the actual migration, users need to:
Provide a name and description for the migration.
Choose the type of migration from a drop-down menu.
During migration, users can:
Map-enabled networks in Guest VMs to OpenStack Networks.
Trilio automatically detects networks, providing a seamless mapping experience.
Users need to:
Map Datastores detected from the migration plan VMs with OpenStack volume types.
This ensures proper mapping of storage resources during migration.
Users must:
Select VMs mapped to the Migration Plan for migration.
For each VM, choose the correct flavor and Availability Zone.
Specify configurations for disks to be created on OpenStack.
For the VMs that are UEFI booted, a glance image must be selected. Refer to this page for more details.
There are certain limitations that have to be taken care of by the user once the migration is successful, please refer to the Limitations page for more information.
Deletion of the initiated Migrations can be done to clean up the unnecessary entries in the list. Please note that deleting a migration does not clean up the migrated VMs or their associated resources from OpenStack. The user will have to explicitly remove the migrated resources if necessary.\
This step-by-step guide provides instructions on running a migration for Virtual Machines (VMs) from VMware to OpenStack.
Before initiating the migration, ensure the following prerequisites are met:
Access to the VMware environment.
OpenStack environment configured and accessible.
created with the desired VMs selected.
Log in to the OpenStack Dashboard (Horizon):
Use your credentials to log in to the OpenStack Dashboard.
Navigate to the VMware Migration section:
In the OpenStack Dashboard, locate and click on the VMware Migration under the Project tab.
Initiate Migration:
If unsure whether the "Migration Plan" has initiated "Discover VMs" or not, it can be re-initiated before starting the migration.
Within the Migration Plan, look for the option Migrate to initiate migration.
It will pop up one wizard for collecting the user inputs.
Provide Migration Details:
Migration Name: Enter a unique and meaningful name for the Migration.
Migration Description: Optionally, add a detailed description to provide context for the migration.
Migration Type: Select the Migration Type from the drop-down. Refer to for more information about the migration types that Trilio supports.
Map the Networks:
This section has a comprehensive list of all the unique networks found in all the VMs that are part of that Migration Plan.
Select the OpenStack networks, to which the VM's networks need to map.
Map the Volume Types:
This section has a comprehensive list of all the unique Datastores found in all the VMs that are part of that Migration Plan.
Select the OpenStack Volume types to which the VM's Datastores need to be mapped.
Select VMs:
Select the VMs of the Migration Plan that needs to be migrated to the OpenStack.
Verify the details of the VM to be migrated by clicking the "+" sign on the VMs.
Start Migration:
Start the migration by clicking the Migrate button.
Observe the results in the OpenStack Dashboard.
Verify that Instances are created with storage volumes, networking, and security groups attached.
Verify if the Instances are booting up.
Post-Migration Tasks:
As mentioned on the page, the user will have to set up the network by accessing the console of the instance.
Test Connectivity:
Validate the connectivity of the VMs created on OpenStack.
The Migration Plan will enter a "Locked" state while its migration is in progress. A new migration for that plan can be initiated once the running migration is available or has encountered an error and the Plan is in an "Available" state.
Congratulations! You have successfully run a migration for VMs from VMware to OpenStack using the specified migration type. Ensure to validate the results and perform necessary tests to confirm the success of the migration process.