The feature addresses a critical user experience gap: users were able to select Warm Migration for VMware environments without having the required VMware vSphere Virtual Disk Development Kit (VDDK) configured, leading to silent failures during the migration execution.

The underlying engineering work adds highly visible, preventative validation checks to the web console.

Technical Writer Scope (Prerequisite Alignment)

The technical writer's primary objective is to align documentation references with this new UI validation behavior. Key areas include:

1. Validation Text Review: Validate the exact wording of the new warning/error message that appears in the migration wizard and the plan details modal.

1. Prerequisite Link Validation: Confirm that the "Learn More" link embedded in the validation message correctly directs the user to the precise section of the documentation detailing the VDDK installation and configuration prerequisites. (The current description provides a target link, which must be verified against the final 2.11 documentation structure).

1. Procedural Update: Ensure that the documentation steps for creating a Warm Migration Plan are updated to explicitly mention the VDDK requirement before the user reaches the validation step, providing a proactive, "tell before you show" experience.

JTBD Statement:

"When I select Warm Migration for my VMware Virtual Machines, I want the web console to immediately warn me if the required VDDK dependency is missing or misconfigured so that I can fix the prerequisite setup proactively and avoid wasting time on a migration plan that is guaranteed to fail later during execution."

Documentation Task

The documentation task (MTV-3804) supports this job by addressing the primary sub-job:

"When I encounter the new VDDK validation warning, I need the linked documentation to be accurate and comprehensive so that I can understand the installation steps for VDDK and quickly return to the migration wizard knowing I've met the technical requirements."

Currently, a user can not do a warm migration when VDDK is not set up, but there is no indication of that.

Goal:

Add validation in:

(1) The migration type step of the wizard

(2) The "Migration type" edit modal in the plan details

The learn more link should link to: https://docs.redhat.com/en/documentation/migration_toolkit_for_virtualization/2.7/html-single/installing_and_using_the_migration_toolkit_for_virtualization/index#vmware-prerequisites_mtv

Figma link 

Ask UX questions to mmenestr