Red Hat OpenStack Administration I: Core Operations for Domain Operators (CL110) — Lesson 2: Images, Flavors, Key Pairs, Instances, Metadata, and Compute Operations

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing Glance images and flavors.
• Implement and validate key pairs, instance lifecycle, and metadata 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

• Glance images applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• flavors applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• key pairs applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• instance lifecycle applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• metadata applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.

Instructor Demonstration

The instructor traces a cloud operations team providing governed self-service infrastructure to multiple internal projects. The walkthrough connects navigation, commands, configuration logic, system messages, and evidence captured in the OpenStack domain operations guide, resource build evidence, access model, and tenant support 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 Images, Flavors, Key Pairs, Instances, Metadata, and Compute Operations and preserve the verified result in the OpenStack domain operations guide, resource build evidence, access model, and tenant support 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 Glance images.
• Compare two defensible responses and explain technical, security, operational, and support trade-offs.
• Determine how the OpenStack domain operations guide, resource build evidence, access model, and tenant support 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 OpenStack domain operations guide, resource build evidence, access model, and tenant support 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 Images, Flavors, Key Pairs, Instances, Metadata, and Compute Operations, explain the resulting platform behavior, and defend the outcome through the OpenStack domain operations guide, resource build evidence, access model, and tenant support checklist.