Feature Overview

The goal of this feature is to extend the os_migrate tool to facilitate the migration of virtual machines (VMs) from VMware to Red Hat OpenShift Service on OpenStack (RHOSO) with minimal downtime. The migration process will focus on stopping the source VMware VM, converting it to the qcow2 KVM format, and moving it to the destination cloud (RHOSO 18.0).

Goals

• Benefit to Users: This feature will benefit system administrators and IT professionals responsible for managing cloud infrastructure by providing a  method to migrate VMs from VMware to RHOSO, minimizing downtime and simplifying the migration process.
• Current State vs. Future State: Currently, VM migration from VMware to RHOSO may involve multiple manual steps and significant downtime. With this feature, the process will be automated and optimized, resulting in less manual intervention and reduced service interruption.

Requirements

Use Cases

• User Interaction: System administrators will use the os_migrate tool's new feature to initiate and complete the migration of VMs from VMware to RHOSO.
• Target Users: This feature is intended for IT professionals responsible for managing virtualized environments and migrating workloads to cloud infrastructure.
• Integration with Current Interface: The feature will be integrated into the current os_migrate tool interface, maintaining consistency and ease of use for existing users.

Out of Scope

• Pre-workload migration tasks such as copying networks, security groups, and images are out of scope for this feature.  We could potentially leverage the work from vmware to OCP virtualization solution to gather the network information facts from the source vSphere cluster: AAP-23015  https://gitlab.consulting.redhat.com/redhat-cop/vmware-openshift-virt-migration/vmware_migr[…]mware_migration/roles/tor_switch_gather?ref_type=heads  and then manually map it to OSP resources.

Assumptions

• Prerequisites and dependencies, such as access to both VMware and RHOSO environments, are in place.
• Necessary hardware and software resources are available for the migration process.

Documentation Considerations

• Educational and Reference Material: Provide documentation for users and admins on how to use the new feature.
• Success Criteria: Success is defined by the ability to migrate VMs from VMware to RHOSO with minimal downtime and user intervention.
• Doc Impact: This feature will require updates to existing content and a release note.

Interoperability Considerations

• Impact on Other Products: Ensure compatibility with other products and versions in the portfolio.
• Test Scenarios: Develop and factor interoperability test scenarios to validate the feature's functionality.

Questions