Preparations

Preparing OpenStack + Trilio

You will need to be ready with below-mentioned resources before starting with the deployment:

VMware Resources

vCenter access information

• vCenter access URL

• vCenter access Username and Password

• SSL certificate for secured connection to VCenter (if not available, the SSL verification has to be marked false during configuration)

• The minimum set of permissions required for a vCenter user to successfully migrate VMs are as follows:

Privilege Level	Required Permissions
Datastore	Browse datastore Low level file operations
Sessions	Validate session
Virtual machine / Interaction	Guest operating system management by VIX API Power off Power on
Virtual machine / Provisioning	Allow disk access Allow read-only disk access Allow virtual machine download
Virtual machine / Snapshot management	Create snapshot Remove snapshot

VMware vSphere Virtual Disk Development Kit 7.0

• Trilio requires this kit for the VM migration feature to work. You can download it from the VMware Customer Connect portal by accessing the below link

• https://customerconnect.vmware.com/downloads/get-download?downloadGroup=VDDK700

• Make sure you download the below-mentioned file

  Product	VMware vSphere Virtual Disk Development Kit 7.0
  Version	7.0
  Release Date	2020-04-02
  Build Number	15832853
  File Name	VMware-vix-disklib-7.0.0-15832853.x86_64.tar.gz

Windows VMs Preparation

• VMware tools need to be installed and should be in running state on all the windows VMs which are to be migrated. Alternatively, the guest OS may be shutdown but they should not be in power off state

OpenStack Resources

Glance Images

• For migrating UEFI booted VMware VMs, the OpenStack requires to have the instances with UEFI boot information and so as Trilio.

• So before doing the migration, the user needs to create a Glance image (any image) with following metadata properties:

  1. set hw_firmware_type property to UEFI

  2. set hw_machine_type property to q35

• This is not required for BIOS booted VMware VMs

Instace Flavors

• Trilio does not create any flavor for the migrating VMs instead it uses the available flavors.

• To avoid any booting issues post-migration, the user needs to have the correct flavors created and available for selection while initiating the migration.

Preparing the Guest VMs on ESXi

To leverage the Dry-run and Warm migration features, the vCenter and ESXi should support the Change Block Tracking(CBT) feature. Make sure that all the data disks attached to the VM, have the CBT enabled.

To enable the CBT, follow the instructions at VMware Knowledge Base

Also understand the limitations Trilio has described in this page.