VMware Virtual Disk Development Kit (VDDK) provides optimized disk transfer capabilities for VMware vSphere migrations. This chapter covers creating VDDK container images and configuring them for maximum performance.

For background information on VDDK and its integration with Forklift, see the official VDDK documentation.

Performance Benefits

VDDK provides significant performance improvements over standard disk transfer methods:

  • Optimized Data Transfer: Direct access to VMware’s optimized disk I/O APIs
  • Reduced Network Overhead: Efficient data streaming and compression
  • Better Throughput: Can achieve 2-5x faster transfer speeds compared to standard methods
  • Resource Efficiency: Lower CPU and memory usage during transfers

Technical Advantages

  • Native VMware Integration: Uses VMware’s official SDK for optimal compatibility
  • Advanced Features: Support for changed block tracking (CBT) and incremental transfers
  • Error Handling: Better error detection and recovery mechanisms
  • Storage Array Integration: Support for storage array offloading when available

When to Use VDDK

  • Production Migrations: Always recommended for production VMware environments
  • Large VMs: Essential for VMs with large disk sizes (>100GB)
  • Performance-Critical: When migration time is a critical factor
  • Storage Array Offloading: When using compatible storage arrays with offloading capabilities

Prerequisites for Building the Image

System Requirements

Before building VDDK images, ensure you have:

  • Container Runtime: Podman or Docker installed and working
  • Kubernetes Registry Access: Access to a container registry (internal or external)
  • File System: A file system that preserves symbolic links (symlinks)
  • Network Access: If using external registries, ensure KubeVirt can access them

VMware License Compliance

Important License Notice
Storing VDDK images in public registries might violate VMware license terms. Always use private registries and ensure compliance with VMware licensing requirements.

Download VDDK SDK

  1. Visit Broadcom Developer Portal: https://developer.broadcom.com/sdks/vmware-virtual-disk-development-kit-vddk/latest
  2. Download VDDK: Get the VMware Virtual Disk Development Kit (VDDK) tar.gz file
  3. Supported Versions: VDDK 8.0.x is recommended for optimal performance
  4. File Verification: Verify the downloaded file integrity if checksums are provided

Runtime Prerequisites

1
2
3
4
5
6
7
8

# Install podman (RHEL/Fedora)
sudo dnf install podman

# Install podman (Ubuntu/Debian)  
sudo apt-get install podman

# Verify podman installation
podman --version

Docker (Alternative)

1
2
3
4
5
6
7
8
9
10
11
12
13

# Install Docker (Ubuntu/Debian)
sudo apt-get update
sudo apt-get install docker.io

# Install Docker (RHEL/Fedora)
sudo dnf install docker

# Start and enable Docker
sudo systemctl start docker
sudo systemctl enable docker

# Verify Docker installation
docker --version

How-To: Building the VDDK Image

Basic VDDK Image Creation

The kubectl mtv create vddk-image command automates the entire VDDK image build process:

1
2
3
4
5
6
7
8
9
10

# Basic VDDK image creation
kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag quay.io/your-registry/vddk:8.0.1

# With automatic push to registry
kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag quay.io/your-registry/vddk:8.0.1 \
  --push

Command Syntax and Options

1

kubectl mtv create vddk-image [OPTIONS]

Required Flags

  • --tar PATH: Path to VMware VDDK tar.gz file (required)
  • --tag IMAGE:TAG: Container image tag (required)

Optional Flags

  • --build-dir PATH: Custom build directory (uses temp directory if not specified)
  • --runtime RUNTIME: Container runtime (auto, podman, docker) - default: auto
  • --platform ARCH: Target platform (amd64, arm64) - default: amd64
  • --dockerfile PATH: Path to custom Dockerfile (uses default if not specified)
  • --push: Push image to registry after successful build
  • --push-insecure-skip-tls: Skip TLS verification when pushing to the registry (podman only, docker requires daemon configuration)
  • --set-controller-image: Configure the pushed image as the global vddk_image in ForkliftController (requires --push)

Detailed Build Examples

Standard Production Build

1
2
3
4
5
6
7

# Production VDDK image with push
kubectl mtv create vddk-image \
  --tar ~/downloads/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag quay.io/company/vddk:8.0.1 \
  --runtime podman \
  --platform amd64 \
  --push

Build, Push, and Configure ForkliftController

The --set-controller-image flag automatically configures the ForkliftController CR with the pushed VDDK image, setting it as the global default for all vSphere providers:

1
2
3
4
5
6
7

# Build, push, and configure as global VDDK image
kubectl mtv create vddk-image \
  --tar ~/downloads/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag quay.io/company/vddk:8.0.1 \
  --runtime podman \
  --push \
  --set-controller-image

This single command:

  1. Builds the VDDK container image
  2. Pushes it to the registry
  3. Patches the ForkliftController CR to set spec.vddk_image to the pushed image

The global vddk_image setting applies to all vSphere providers unless they have a per-provider vddkInitImage override configured.

Custom Build Directory

1
2
3
4
5
6
7

# Use specific build directory for large environments
kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag harbor.company.com/migration/vddk:latest \
  --build-dir /tmp/vddk-build \
  --runtime podman \
  --push

Multi-Architecture Build

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

# Build for ARM64 architecture
kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag quay.io/company/vddk:8.0.1-arm64 \
  --platform arm64 \
  --runtime podman \
  --push

# Build for AMD64 architecture (default)
kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag quay.io/company/vddk:8.0.1-amd64 \
  --platform amd64 \
  --runtime podman \
  --push

Custom Dockerfile Build

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18

# Create custom Dockerfile with additional tools
cat > custom-vddk.dockerfile << 'EOF'
FROM registry.redhat.io/ubi8/ubi:latest

# Install additional debugging tools
RUN dnf install -y tcpdump netstat-ng && dnf clean all

# Copy VDDK libraries (will be handled by kubectl-mtv)
# Additional customizations can be added here

EOF

# Build with custom Dockerfile
kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag quay.io/company/vddk:8.0.1-custom \
  --dockerfile custom-vddk.dockerfile \
  --push

Different Container Runtimes

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

# Force use of Docker
kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag localhost:5000/vddk:8.0.1 \
  --runtime docker \
  --push

# Force use of Podman
kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag quay.io/company/vddk:8.0.1 \
  --runtime podman \
  --push

# Auto-detect runtime (default)
kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag quay.io/company/vddk:8.0.1 \
  --runtime auto \
  --push

Insecure Registry Push

For registries with self-signed certificates or internal registries without valid TLS certificates:

1
2
3
4
5
6
7

# Push to insecure registry with Podman (recommended)
kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag internal-registry.local:5000/vddk:8.0.1 \
  --runtime podman \
  --push \
  --push-insecure-skip-tls

Note: The --push-insecure-skip-tls flag works natively with Podman by adding --tls-verify=false to the push command. Docker does not support per-command TLS skip and requires daemon configuration instead.

Docker Configuration for Insecure Registries:

If using Docker, configure your daemon before pushing:

1
2
3
4
5
6
7

# Edit /etc/docker/daemon.json
{
  "insecure-registries": ["internal-registry.local:5000"]
}

# Restart Docker
sudo systemctl restart docker

Build Process Verification

1
2
3
4
5
6
7
8
9
10

# Verify image was built successfully
podman images | grep vddk
# or
docker images | grep vddk

# Test image functionality
podman run --rm quay.io/company/vddk:8.0.1 /usr/bin/vmware-vdiskmanager -h

# Verify image layers and size
podman inspect quay.io/company/vddk:8.0.1

VDDK Configuration Hierarchy

VDDK images can be configured at multiple levels. Understanding the hierarchy helps you choose the right approach:

Configuration Levels (in order of precedence)

  1. Per-Provider Setting (highest priority): Set via --vddk-init-image flag when creating a provider
  2. ForkliftController Global Setting: Set via --set-controller-image flag or by patching the ForkliftController CR
  3. Environment Variable Default: Set via MTV_VDDK_INIT_IMAGE (used as default when creating providers)

When to Use Each Level

Level Use Case
Per-Provider Different VDDK versions for specific vCenters, testing new versions
ForkliftController Organization-wide default, single source of truth for all migrations
Environment Variable Local development, CLI defaults for provider creation

Configuring ForkliftController Global VDDK Image

The ForkliftController CR can be configured with a global VDDK image that applies to all vSphere providers:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15

# Option 1: Set during VDDK image build (recommended)
kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag quay.io/company/vddk:8.0.1 \
  --push \
  --set-controller-image

# Option 2: Manually patch the ForkliftController
kubectl patch forkliftcontroller forklift-controller -n openshift-mtv \
  --type merge \
  -p '{"spec":{"vddk_image":"quay.io/company/vddk:8.0.1"}}'

# Verify the configuration
kubectl get forkliftcontroller forklift-controller -n openshift-mtv \
  -o jsonpath='{.spec.vddk_image}'

Setting the MTV_VDDK_INIT_IMAGE Environment Variable

Setting the Default VDDK Image

The MTV_VDDK_INIT_IMAGE environment variable provides a default for vSphere provider creation with kubectl mtv:

1
2
3
4
5

# Set the default VDDK image
export MTV_VDDK_INIT_IMAGE=quay.io/your-registry/vddk:8.0.1

# Verify the environment variable
echo $MTV_VDDK_INIT_IMAGE

Persistent Configuration

Shell Profile Configuration

1
2
3
4
5
6
7

# Add to ~/.bashrc for bash users
echo 'export MTV_VDDK_INIT_IMAGE=quay.io/your-registry/vddk:8.0.1' >> ~/.bashrc
source ~/.bashrc

# Add to ~/.zshrc for zsh users
echo 'export MTV_VDDK_INIT_IMAGE=quay.io/your-registry/vddk:8.0.1' >> ~/.zshrc
source ~/.zshrc

System-wide Configuration

1
2
3
4
5
6
7
8
9

# Create system-wide environment file
sudo tee /etc/environment.d/mtv-vddk.conf << EOF
MTV_VDDK_INIT_IMAGE=quay.io/your-registry/vddk:8.0.1
EOF

# Or add to /etc/profile.d/
sudo tee /etc/profile.d/mtv-vddk.sh << EOF
export MTV_VDDK_INIT_IMAGE=quay.io/your-registry/vddk:8.0.1
EOF

Container/Pod Environment

1
2
3
4
5
6
7
8
9
10
11
12
13

# For containerized kubectl-mtv usage
docker run -e MTV_VDDK_INIT_IMAGE=quay.io/your-registry/vddk:8.0.1 \
  kubectl-mtv-image create provider vsphere-prod --type vsphere

# In Kubernetes pods
apiVersion: v1
kind: Pod
spec:
  containers:
  - name: kubectl-mtv
    env:
    - name: MTV_VDDK_INIT_IMAGE
      value: "quay.io/your-registry/vddk:8.0.1"

Environment Variable Validation

1
2
3
4
5
6
7
8
9
10
11
12
13

# Verify environment variable is set
if [ -z "$MTV_VDDK_INIT_IMAGE" ]; then
  echo "MTV_VDDK_INIT_IMAGE is not set"
else
  echo "MTV_VDDK_INIT_IMAGE is set to: $MTV_VDDK_INIT_IMAGE"
fi

# Test with provider creation (should use default image)
kubectl mtv create provider vsphere-test --type vsphere \
  --url https://vcenter.test.com/sdk \
  --username admin \
  --password password123 \
  --dry-run

Using the VDDK Image in Provider Creation

Automatic VDDK Image Usage

When MTV_VDDK_INIT_IMAGE is set, providers automatically use the VDDK image:

1
2
3
4
5

# This will automatically use the VDDK image from MTV_VDDK_INIT_IMAGE
kubectl mtv create provider vsphere-auto --type vsphere \
  --url https://vcenter.example.com/sdk \
  --username administrator@vsphere.local \
  --password YourPassword

Explicit VDDK Image Specification

Override the default VDDK image per provider:

1
2
3
4
5
6

# Use specific VDDK image for this provider
kubectl mtv create provider vsphere-custom --type vsphere \
  --url https://vcenter.example.com/sdk \
  --username administrator@vsphere.local \
  --password YourPassword \
  --vddk-init-image quay.io/company/vddk:8.0.2

VDDK Performance Optimization

Enable advanced VDDK optimization features:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

# Provider with VDDK AIO optimization
kubectl mtv create provider vsphere-optimized --type vsphere \
  --url https://vcenter.example.com/sdk \
  --username administrator@vsphere.local \
  --password YourPassword \
  --vddk-init-image quay.io/company/vddk:8.0.1 \
  --use-vddk-aio-optimization

# Provider with custom VDDK buffer settings
kubectl mtv create provider vsphere-tuned --type vsphere \
  --url https://vcenter.example.com/sdk \
  --username administrator@vsphere.local \
  --password YourPassword \
  --vddk-init-image quay.io/company/vddk:8.0.1 \
  --use-vddk-aio-optimization \
  --vddk-buf-size-in-64k 128 \
  --vddk-buf-count 16

VDDK Configuration Parameters

Buffer Size Optimization

The --vddk-buf-size-in-64k parameter controls the buffer size in 64KB units:

1
2
3
4
5
6
7
8
9
10
11

# Small VMs (default - automatic sizing)
--vddk-buf-size-in-64k 0

# Medium VMs (8MB buffer)
--vddk-buf-size-in-64k 128

# Large VMs (16MB buffer)
--vddk-buf-size-in-64k 256

# Very large VMs (32MB buffer)
--vddk-buf-size-in-64k 512

Buffer Count Tuning

The --vddk-buf-count parameter controls the number of parallel buffers:

1
2
3
4
5
6
7
8
9
10
11

# Low concurrency (default)
--vddk-buf-count 0

# Medium concurrency
--vddk-buf-count 8

# High concurrency
--vddk-buf-count 16

# Maximum concurrency (use with caution)
--vddk-buf-count 32

Complete VDDK Workflow Examples

Example 1: Enterprise Production Setup

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31

# Step 1: Download VDDK from VMware
# (Manual step - download VMware-vix-disklib-distrib-8.0.1.tar.gz)

# Step 2: Build, push, and configure ForkliftController with VDDK image
kubectl mtv create vddk-image \
  --tar ~/downloads/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag harbor.company.com/migration/vddk:8.0.1 \
  --runtime podman \
  --platform amd64 \
  --push \
  --set-controller-image

# Step 3: (Optional) Also set environment variable for CLI defaults
export MTV_VDDK_INIT_IMAGE=harbor.company.com/migration/vddk:8.0.1
echo 'export MTV_VDDK_INIT_IMAGE=harbor.company.com/migration/vddk:8.0.1' >> ~/.bashrc

# Step 4: Create optimized vSphere provider (will use global VDDK image from controller)
kubectl mtv create provider vsphere-production --type vsphere \
  --url https://vcenter.prod.company.com/sdk \
  --username svc-migration@vsphere.local \
  --password $(cat /secure/vsphere-password) \
  --use-vddk-aio-optimization \
  --vddk-buf-size-in-64k 256 \
  --vddk-buf-count 16

# Step 5: Verify VDDK integration
kubectl mtv describe provider vsphere-production | grep -i vddk

# Step 6: Verify ForkliftController configuration
kubectl get forkliftcontroller forklift-controller -n openshift-mtv \
  -o jsonpath='{.spec.vddk_image}'

Example 2: Multi-Architecture Deployment

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

# Build for both AMD64 and ARM64
kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag quay.io/company/vddk:8.0.1-amd64 \
  --platform amd64 \
  --push

kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag quay.io/company/vddk:8.0.1-arm64 \
  --platform arm64 \
  --push

# Create manifest list for multi-arch support
podman manifest create quay.io/company/vddk:8.0.1
podman manifest add quay.io/company/vddk:8.0.1 quay.io/company/vddk:8.0.1-amd64
podman manifest add quay.io/company/vddk:8.0.1 quay.io/company/vddk:8.0.1-arm64
podman manifest push quay.io/company/vddk:8.0.1

# Use multi-arch image
export MTV_VDDK_INIT_IMAGE=quay.io/company/vddk:8.0.1

Example 3: Development and Testing

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37

# Build test VDDK image with debugging tools
cat > debug-vddk.dockerfile << 'EOF'
FROM registry.redhat.io/ubi8/ubi:latest

# Install debugging and monitoring tools
RUN dnf install -y \
    tcpdump \
    netstat-ng \
    iotop \
    htop \
    strace \
    && dnf clean all

# Install additional utilities
RUN dnf install -y \
    curl \
    wget \
    telnet \
    && dnf clean all
EOF

# Build with debugging tools
kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag localhost:5000/vddk:debug \
  --dockerfile debug-vddk.dockerfile \
  --runtime podman \
  --push

# Create test provider with debug image
kubectl mtv create provider vsphere-debug --type vsphere \
  --url https://vcenter-test.internal/sdk \
  --username administrator@vsphere.local \
  --password TestPassword \
  --vddk-init-image localhost:5000/vddk:debug \
  --provider-insecure-skip-tls \
  -n testing

Advanced VDDK Configuration

Registry Authentication

For private registries, ensure proper authentication:

1
2
3
4
5
6
7
8
9
10
11
12
13
14

# Login to registry
podman login quay.io
# or
docker login quay.io

# Create registry secret in Kubernetes
kubectl create secret docker-registry vddk-registry-secret \
  --docker-server=quay.io \
  --docker-username=your-username \
  --docker-password=your-password \
  --docker-email=your-email@company.com

# Use secret in migration namespace
kubectl patch serviceaccount default -p '{"imagePullSecrets": [{"name": "vddk-registry-secret"}]}'

Performance Monitoring and Tuning

VDDK Performance Metrics

1
2
3
4
5
6
7
8

# Monitor VDDK pod performance during migration
kubectl top pods -l app=vddk

# Check VDDK container logs
kubectl logs -l app=vddk -f

# Monitor network usage
kubectl exec -it vddk-pod -- netstat -i

Buffer Tuning Guidelines

VM Size Buffer Size (64K units) Buffer Count Total Memory
Small (< 50GB) 64 4 16MB
Medium (50-200GB) 128 8 64MB
Large (200-500GB) 256 16 256MB
Very Large (> 500GB) 512 32 1GB 
1
2
3
4
5
6
7
8
9

# Apply tuning based on VM size
kubectl mtv create provider vsphere-large-vms --type vsphere \
  --url https://vcenter.example.com/sdk \
  --username admin \
  --password password \
  --vddk-init-image quay.io/company/vddk:8.0.1 \
  --use-vddk-aio-optimization \
  --vddk-buf-size-in-64k 512 \
  --vddk-buf-count 32

Storage Array Offloading

For compatible storage arrays, enable offloading:

1
2
3
4
5
6
7
8
9
10
11
12
13

# Provider with storage array offloading
kubectl mtv create provider vsphere-offload --type vsphere \
  --url https://vcenter.example.com/sdk \
  --username admin \
  --password password \
  --vddk-init-image quay.io/company/vddk:8.0.1 \
  --use-vddk-aio-optimization

# Use with storage mapping that supports offloading
kubectl mtv create mapping storage offload-mapping \
  --source vsphere-offload \
  --target openshift \
  --storage-pairs "datastore1:fast-ssd;offloadPlugin=vsphere;offloadVendor=flashsystem"

Troubleshooting VDDK Issues

Common Build Problems

VDDK Tar File Issues

1
2
3
4
5
6

# Verify VDDK tar file integrity
file ~/VMware-vix-disklib-distrib-8.0.1.tar.gz
tar -tzf ~/VMware-vix-disklib-distrib-8.0.1.tar.gz | head -10

# Check file permissions
ls -la ~/VMware-vix-disklib-distrib-8.0.1.tar.gz

Container Runtime Issues

1
2
3
4
5
6
7

# Test container runtime
podman --version
podman run hello-world

# Check registry connectivity
podman login quay.io
podman pull registry.redhat.io/ubi8/ubi:latest

Build Directory Problems

1
2
3
4
5
6
7
8
9

# Check available disk space
df -h /tmp

# Use custom build directory with more space
mkdir -p /data/vddk-build
kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag quay.io/company/vddk:8.0.1 \
  --build-dir /data/vddk-build

Runtime Issues

Image Pull Problems

1
2
3
4
5
6
7
8

# Test image accessibility
podman pull quay.io/company/vddk:8.0.1

# Check image manifest
podman inspect quay.io/company/vddk:8.0.1

# Verify registry credentials
kubectl get secret vddk-registry-secret -o yaml

Performance Issues

1
2
3
4
5
6
7
8

# Monitor VDDK container resource usage
kubectl top pods -l app=vddk

# Check for resource constraints
kubectl describe pod vddk-pod-name

# Verify VDDK buffer settings
kubectl get provider vsphere-prod -o yaml | grep -A5 vddk

Debug and Logging

1
2
3
4
5
6
7
8
9
10
11
12
13

# Enable verbose logging for VDDK builds
kubectl mtv create vddk-image \
  --tar ~/VMware-vix-disklib-distrib-8.0.1.tar.gz \
  --tag quay.io/company/vddk:debug \
  -v=2

# Test VDDK functionality
podman run --rm quay.io/company/vddk:8.0.1 \
  /usr/bin/vmware-vdiskmanager -h

# Check VDDK library versions
podman run --rm quay.io/company/vddk:8.0.1 \
  find /opt -name "*.so" -exec ls -la {} \;

Best Practices Summary

Security

  • Always use private registries for VDDK images
  • Implement proper registry authentication
  • Follow VMware licensing requirements
  • Use least-privilege access for registry credentials

Performance

  • Use VDDK 8.0.x for optimal performance
  • Enable AIO optimization for production
  • Tune buffer sizes based on VM characteristics
  • Monitor and adjust based on actual performance

Operations

  • Automate VDDK image builds in CI/CD pipelines
  • Version VDDK images with semantic versioning
  • Test images thoroughly before production deployment
  • Maintain separate images for different environments

Next Steps

After configuring VDDK:

  1. Explore Inventory: Discover VMs and resources in Chapter 7: Inventory Management
  2. Create Mappings: Configure resource mappings in Chapter 9: Mapping Management
  3. Optimize Performance: Learn advanced techniques in Chapter 13: Migration Process Optimization
  4. Plan Migrations: Create optimized plans in Chapter 10: Migration Plan Creation

Previous: Chapter 5: Migration Host Management
Next: Chapter 7: Inventory Management