Similarly to the storage offload efforts, we should integrate MTV with the NetApp.
NetApp can't follow the storage offload as it does not work with the LUNs, which would get attached to the ESXi hosts, but it works with file-based storage NFS.

Why? To improve migration speeds, MTV needs the storage vendor integration for faster migration times.

Docs

This ticket covers the documentation requirements for the integration of the Migration Toolkit for Virtualization (MTV) with NetApp ONTAP (Shift). This integration is designed to significantly enhance migration performance for workloads utilizing NetApp storage.

Unlike general storage copy offload features which typically interface with Block storage/LUNs, the NetApp integration focuses on file-based storage (NFS). By leveraging NetApp’s native capabilities, MTV can bypass standard data copy bottlenecks, resulting in faster migration times for virtual machines whose disks reside on NetApp NFS exports.

Jobs to Be Done (JTBD)

• When I am migrating large virtual machine workloads from a VMware environment backed by NetApp NFS storage, I want to leverage native NetApp storage integration within MTV, so that I can achieve significantly higher data transfer speeds and reduce the overall migration window.

User Stories

• As a Storage/Cluster Administrator, I want to configure MTV to recognize NetApp-backed NFS storage so that I can utilize vendor-specific optimizations for data transfer.

• As a Migration Engineer, I want clear instructions on the prerequisites and configuration steps for NetApp Shift integration to ensure a successful, high-performance migration without the overhead of standard network-based disk copying.

Core Goals & Scope

• Technical Integration: Document how MTV interfaces with NetApp Shift for file-based NFS storage rather than Block/LUN-based offloading.

• Performance Optimization: Highlight the performance benefits and expected improvements in migration speed when using this integration.

• Configuration Procedures: Provide step-by-step guides for enabling this integration within the MTV User Interface and via CRD configuration.

• Prerequisites: Detail any specific NetApp ONTAP or network requirements (e.g., specific API permissions or NFS mount settings).

Technical Considerations

• Fix Version: 2.11.0.

• Dependency: This task is closely related to MTV-3138 (Integration of NetApp Shift into MTV).

• Information Sources: Final documentation is pending technical design details from mnecas@redhat.com, rgolan1@redhat.com, and gcheresh@redhat.com.

• Compatibility: Integration must align with existing MTV provider and storage mapping workflows.

Technical specifics required to ensure accurate documentation:

1. Storage Environment Prerequisites

• ONTAP Version: What are the minimum and recommended versions of NetApp ONTAP supported for this integration?

• Export Requirements: Are there specific NFS export policies or flags required on the NetApp side (e.g., no_root_squash, specific R/W permissions)?

• NFS Protocol: Is this limited to NFS v3, or is NFS v4.x supported?

2. Connectivity & Port Requirements

• New Network Ports: Does this integration require traffic over ports other than standard NFS (2049) or RPC Portmapper (111)?

• API Communication: Which port and protocol are used for MTV to communicate with the NetApp ONTAP API?

• Network Path: Does the integration require direct connectivity between the OpenShift nodes and the NetApp management interface?
   

3. Authentication & Security

• Credentials: What type of credentials must the user provide? (e.g., standard Username/Password or Application-specific API tokens?)
   
• Roles/Privileges: What is the minimum set of privileges required on the NetApp controller? (Please provide a list similar to the VMware privileges table).
   
• Certificates: Does the integration support custom CA certificates or "Skip certificate validation" toggles in the UI?
   

4. Configuration Elements (ForkliftController CR)

• New Parameters: What new parameters are being added to the forklift-controller spec?
   
• Feature Gates: Is there a specific feature gate string (e.g., feature_netapp_shift: "true") required to enable the integration in the CR?
   

5. Workflow Differences

• Storage Mapping: In the UI, will users select "NetApp Shift" as an Offload plugin within the existing Storage Map form, or is this a completely new provider type?
   
• Conversion Pods: Does this integration bypass the standard virt-v2v conversion pod, or does it utilize it for finishing tasks after the NetApp data transfer?