DO316 – Managing Virtual Machines with Red Hat OpenShift Virtualization — Lesson 2: Compute, Networking, Storage, Data Volumes, and Guest Configuration

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing CPU and memory and VM networking.
• Implement and validate storage classes, data volumes, and cloud-init using reviewable evidence.
• Evaluate the condition where a change succeeds in one environment but fails elsewhere because inventory, policy, version, or runtime assumptions differ and select a proportionate corrective response.

Detailed Topics

• CPU and memory applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• VM networking applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• storage classes applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• data volumes applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• cloud-init applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces a virtualization team onboarding traditional virtual machines to a shared OpenShift platform. The walkthrough connects navigation, commands, configuration logic, system messages, and evidence captured in the OpenShift Virtualization operating model, VM deployment records, migration plan, and recovery checklist. It also tests the exception where a change succeeds in one environment but fails elsewhere because inventory, policy, version, or runtime assumptions differ.

Hands-On Exercise

Complete a controlled Red Hat exercise covering Compute, Networking, Storage, Data Volumes, and Guest Configuration and preserve the verified result in the OpenShift Virtualization operating model, VM deployment records, migration plan, and recovery checklist.

1. Confirm scope, prerequisites, versions, identities, dependencies, and acceptance criteria.
2. Execute the workflow while recording commands, settings, outputs, events, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception.
4. Document corrections, evidence, ownership, retest criteria, rollback, and handover actions.

Scenario Analysis

• Identify which object, service, policy, setting, or sequence most strongly influences CPU and memory.
• Compare two defensible responses and explain technical, security, operational, and support trade-offs.
• Determine how the OpenShift Virtualization operating model, VM deployment records, migration plan, and recovery checklist should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected behavior first differs from the observed result. Check prerequisites, identity, configuration order, version compatibility, connectivity, status, resource limits, and evidence separately. Treat “a change succeeds in one environment but fails elsewhere because inventory, policy, version, or runtime assumptions differ” as a hypothesis until commands, logs, settings, and retest outcomes confirm the cause.

Validation Checklist

• Required platform components, identities, permissions, settings, and dependencies are present.
• The OpenShift Virtualization operating model, VM deployment records, migration plan, and recovery checklist connects each conclusion to objective, reviewable evidence.
• Normal processing, a boundary condition, dependency behavior, and the stated exception were tested.
• Corrections, ownership, retest criteria, rollback, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Compute, Networking, Storage, Data Volumes, and Guest Configuration, explain the resulting platform behavior, and defend the outcome through the OpenShift Virtualization operating model, VM deployment records, migration plan, and recovery checklist.