DO346 – Migrating Virtual Machines to Red Hat OpenShift Virtualization with Ansible Automation Platform — Lesson 2: Migration Toolkit, Provider Setup, Network and Storage Mappings, and Plans

Learning Objectives

• Configure the principal services, objects, workflows, and controls for Migration Toolkit, provider configuration, and network mappings.
• Apply storage mappings and migration plans while preserving reviewable technical evidence.
• Recognize and correct the condition where a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect.

Detailed Topics

• Migration Toolkit: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• provider configuration: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• network mappings: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• storage mappings: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• migration plans: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.

Instructor Demonstration

The instructor demonstrates migration toolkit, provider setup, network and storage mappings, and plans by tracing architecture, commands, configuration, system messages, and evidence. The walkthrough tests how a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect and explains how to isolate the cause without masking related issues.

Hands-On Exercise

Implement the core workflow for Migration Toolkit, Provider Setup, Network and Storage Mappings, and Plans and add the verified result to the migration inventory, mapping design, Ansible workflow, wave test results, rollback plan, and cutover runbook.

1. Confirm scope, versions, access, dependencies, assumptions, and acceptance criteria.
2. Perform the workflow while recording commands, configuration, output, events, and decisions.
3. Test the normal path and one course-specific exception or boundary condition.
4. Retest the correction and document rollback, ownership, and follow-up actions.

Scenario Analysis

• Identify which dependency most strongly influences Migration Toolkit in the stated scenario.
• Compare two approaches for storage mappings and explain the security, reliability, performance, and support trade-offs.
• Decide what evidence must be retained in the migration inventory, mapping design, Ansible workflow, wave test results, rollback plan, and cutover runbook before operational acceptance.

Troubleshooting Guidance

Begin with the first observable difference from the expected result. Check configuration, permissions, sequence, connectivity, and functional behavior separately, then correlate logs, events, commands, metrics, and configuration history. Treat the assumption that a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect as a hypothesis until a reproducible retest confirms the cause.

Validation Checklist

• The required configuration, permissions, sequence, connectivity, and functional behavior were checked and recorded.
• The normal path and a course-specific exception were tested.
• The migration inventory, mapping design, Ansible workflow, wave test results, rollback plan, and cutover runbook links conclusions to commands, configuration, logs, metrics, or other objective evidence.
• Corrective actions, rollback, ownership, and handover notes are complete.

Lesson Outcome

Learners can apply Migration Toolkit, Provider Setup, Network and Storage Mappings, and Plans, explain the observed platform behavior, and support the result with a reviewable migration inventory, mapping design, Ansible workflow, wave test results, rollback plan, and cutover runbook.