DO346 – Migrating Virtual Machines to Red Hat OpenShift Virtualization with Ansible Automation Platform — Lesson 1: Migration Discovery, Source Inventory, Application Dependencies, and Readiness

Learning Objectives

• Explain the architecture, purpose, dependencies, and expected behavior of source discovery, VM inventory, and application dependencies.
• Apply compatibility and readiness while preserving reviewable technical evidence.
• Recognize and correct the condition where an unstated prerequisite or ownership gap causes the initial design to be incomplete.

Detailed Topics

• source discovery: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• VM inventory: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• application dependencies: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• compatibility: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• readiness: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.

Instructor Demonstration

The instructor demonstrates migration discovery, source inventory, application dependencies, and readiness by tracing architecture, commands, configuration, system messages, and evidence. The walkthrough tests how an unstated prerequisite or ownership gap causes the initial design to be incomplete and explains how to isolate the cause without masking related issues.

Hands-On Exercise

Establish a controlled baseline for Migration Discovery, Source Inventory, Application Dependencies, and Readiness 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 source discovery in the stated scenario.
• Compare two approaches for compatibility 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 architecture, scope, identities, prerequisites, and starting conditions separately, then correlate logs, events, commands, metrics, and configuration history. Treat the assumption that an unstated prerequisite or ownership gap causes the initial design to be incomplete as a hypothesis until a reproducible retest confirms the cause.

Validation Checklist

• The required architecture, scope, identities, prerequisites, and starting conditions 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 Discovery, Source Inventory, Application Dependencies, and Readiness, 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.