Red Hat OpenStack Administration II: Day 2 Operations for Cloud Operators (CL210) — Lesson 2: Compute, Images, Placement, Scheduling, Storage, and Capacity Operations

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing Nova compute and Glance.
• Implement and validate Placement, scheduling, and Cinder operations 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

• Nova compute applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• Glance applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• Placement applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• scheduling applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• Cinder operations applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces a cloud operator maintaining a resilient OpenStack environment after initial deployment. The walkthrough connects navigation, commands, configuration logic, system messages, and evidence captured in the OpenStack day-two operations runbook, maintenance plan, monitoring evidence, and incident recovery record. 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, Images, Placement, Scheduling, Storage, and Capacity Operations and preserve the verified result in the OpenStack day-two operations runbook, maintenance plan, monitoring evidence, and incident recovery record.

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 Nova compute.
• Compare two defensible responses and explain technical, security, operational, and support trade-offs.
• Determine how the OpenStack day-two operations runbook, maintenance plan, monitoring evidence, and incident recovery record 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 OpenStack day-two operations runbook, maintenance plan, monitoring evidence, and incident recovery record 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, Images, Placement, Scheduling, Storage, and Capacity Operations, explain the resulting platform behavior, and defend the outcome through the OpenStack day-two operations runbook, maintenance plan, monitoring evidence, and incident recovery record.