Feature Overview (mandatory - Complete while in New status)

The Red Hat OpenStack VMware Migration Toolkit addresses a major pain point in large-scale migrations: the "Double-Data" penalty. Traditionally, migrating a VM requires copying the entire disk from the source array, through the conversion host, and back into the destination storage. This creates massive network stress and requires temporary storage capacity equal to twice the size of the production data.

By implementing NFS Storage Offloading, the toolkit enables the conversion host to directly consume VMware virtual machine disks (.vmdk) from a locally mounted NFS share. This "Zero-Copy" approach allows the toolkit to read directly from the source storage (HPE Nimble, Alletra, Primera, Pure Storage, etc.), eliminating unnecessary data hops and drastically reducing the time required for a VM to become operational in OpenStack.

Goals (mandatory - Complete while in New status)

• Reduce Capacity Requirements: Eliminate the need for massive "buffer" storage typically required to hold intermediate copies of VM disks.

• Accelerate "Time-to-Boot": Enable faster VM starts in OpenStack by optimizing the path between source and destination storage.

• Outcome: Drastically reduced migration windows and lower TCO (Total Cost of Ownership) for the migration infrastructure.

Requirements (mandatory -_ Complete while in Refinement status):

Done - Acceptance Criteria (mandatory - Complete while in Refinement status):

• The Red Hat OpenStack VMware Migration Toolkit completes a migration without triggering VDDK network traffic on port 902.

• Total storage consumption during migration does not exceed the size of the source VM plus the destination disk (no intermediate third copy).

• Migration throughput is limited only by the storage backplane, not the conversion host's management network.

• Successful VM power-on in OpenStack immediately following the direct-path transfer.

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):

• Mount: The Admin mounts the VMware NFS Datastore directly to the Conversion Host.

• Declare: The import_workloads_local_disk_path: "/srv/nfs" variable is set.

• Transfer: The Toolkit reads the .vmdk file directly from the source storage via the mount and writes it to the destination.

• Result: Data movement is halved, and network "stress" is minimized.

Out of Scope __(Initial completion while in Refinement status):

• Automated Provisioning: This feature does not include the automated provisioning of NFS exports on the storage arrays themselves.

• Non-NFS SAN: Direct offloading for Fiber Channel (FC) or iSCSI VMFS volumes (requires a different technical approach).

Documentation Considerations __(Initial completion while in Refinement status):
Performance Tuning Guide: Add a chapter on "Reducing Network Stress via NFS Offloading."

Questions to Answer __(Initial completion while in Refinement status):
Include a list of refinement / architectural questions that may need to be answered before coding can begin.
<your text here>

Background and Strategic Fit (Initial completion while in Refinement status):
This feature is essential for customers moving away from VMware who are facing "Migration Fatigue" due to long waiting times. By treating storage as a first-class citizen in the migration path, the Red Hat OpenStack VMware Migration Toolkit provides an enterprise-grade solution that respects the physical limits of the customer's network and storage hardware.

Customer Considerations __(Initial completion while in Refinement status):
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
<your text here>

Team Sign Off (Completion while in Planning status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

• …