Red Hat OpenStack Administration I: Core Operations for Domain Operators (CL110) — Lesson 3: Networks, Subnets, Routers, Floating IPs, Security Groups, and Connectivity

Learning Objectives

• Explain the structures, services, data, settings, roles, and dependencies governing Neutron networks and subnets.
• Implement and validate routers, floating IPs, and security groups using reviewable evidence.
• Evaluate the condition where operators cannot explain the outcome because logs, commands, settings, and acceptance evidence were not captured consistently and select a proportionate corrective response.

Detailed Topics

• Neutron networks applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• subnets applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• routers applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• floating IPs applied to the course scenario, expected platform behavior, dependencies, controls, and evidence.
• security groups 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 operators cannot explain the outcome because logs, commands, settings, and acceptance evidence were not captured consistently.

Hands-On Exercise

Complete a controlled Red Hat exercise covering Networks, Subnets, Routers, Floating IPs, Security Groups, and Connectivity 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 Neutron networks.
• 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 “operators cannot explain the outcome because logs, commands, settings, and acceptance evidence were not captured consistently” 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 Networks, Subnets, Routers, Floating IPs, Security Groups, and Connectivity, explain the resulting platform behavior, and defend the outcome through the OpenStack domain operations guide, resource build evidence, access model, and tenant support checklist.