Goal

Today, the create provider form is cluttered and not user-friendly

After this epic, the experience of creating providers will be cleaner and easier to understand

User Stories

• As a cluster administrator,
  I want to create a provider easily,
  so that I can create plans to migrate my VMs.

This documentation task focuses on the complete redesign of the Create Provider workflow within the Migration Toolkit for Virtualization (MTV). The update transitions the interface from a complex, single-page form to a streamlined, intuitive experience, reducing the barrier to entry for establishing migration sources and targets.

Ticket Description: [DOC] Enhance Create Provider Form (MTV-3739)

Overview

The "Create Provider" form is the critical first step in the migration lifecycle, where users connect MTV to source environments (e.g., VMware vSphere, oVirt, OpenStack) and destination targets (OpenShift Virtualization).

Previously, this form was identified as "cluttered," presenting all configuration fields—regardless of the provider type—in a way that increased the likelihood of configuration errors. The 2.11.0 release introduces a refactored UI/UX that optimizes the layout based on the specific provider selected, hiding irrelevant fields and providing clearer guidance on required credentials and endpoints.

Scope of Documentation Task

• Procedure Updates: Rewrite the "Adding Providers" section in the Installing and Using MTV guide. The documentation must reflect the new, cleaner layout and any multi-step or categorized data entry fields.

• Visual Audit: Replace all legacy screenshots of the "Create Provider" modal/page with the updated 2.11.0 interface.

• Field Mapping: Ensure that documentation clearly defines the required inputs for each provider type (URL, Username, Password, CA Certificate) as they appear in the new UI.

• Coordination: Align with MTV-3740 to ensure the Release Notes accurately highlight the improved usability as a key feature of the 2.11.0 GA release.

Persona: The Infrastructure Administrator

Role Description: This persona is a technical specialist responsible for managing hybrid cloud environments and orchestrating the movement of hundreds of Virtual Machines.

• Focus: Speed of deployment and accuracy of configuration.

• Pain Points: They are often frustrated by "noisy" interfaces that require them to hunt for the specific fields relevant to their source environment (e.g., distinguishing between vCenter thumbprints vs. oVirt CA certificates).

• Behavior: They prefer a "clean room" UI approach where they only see what is necessary for the task at hand.

Job to Be Done (JTBD) Statement

When I am connecting a new source or destination provider to the Migration Toolkit, I want to use a clean, context-aware configuration form so that I can accurately provide the necessary credentials and endpoints without being distracted by irrelevant fields, allowing me to proceed to migration planning faster.

Documentation Strategy & Impact