DO370 – Enterprise Kubernetes Storage with Red Hat OpenShift Data Foundation — Lesson 2: Storage Classes, Block, File, Object Services, and Workload Integration

Learning Objectives

• Configure the principal services, objects, workflows, and controls for storage classes, block storage, and file storage.
• Apply object storage and workload integration while preserving reviewable technical evidence.
• Recognize and correct the condition where a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect.

Detailed Topics

• storage classes: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• block storage: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• file storage: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• object storage: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.
• workload integration: apply the concept to the course scenario, identify dependencies and controls, and record objective evidence of the result.

Instructor Demonstration

The instructor demonstrates storage classes, block, file, object services, and workload integration by tracing architecture, commands, configuration, system messages, and evidence. The walkthrough tests how a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect and explains how to isolate the cause without masking related issues.

Hands-On Exercise

Implement the core workflow for Storage Classes, Block, File, Object Services, and Workload Integration and add the verified result to the ODF deployment design, storage-class catalog, workload tests, monitoring evidence, and recovery procedure.

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 storage classes in the stated scenario.
• Compare two approaches for object storage and explain the security, reliability, performance, and support trade-offs.
• Decide what evidence must be retained in the ODF deployment design, storage-class catalog, workload tests, monitoring evidence, and recovery procedure before operational acceptance.

Troubleshooting Guidance

Begin with the first observable difference from the expected result. Check configuration, permissions, sequence, connectivity, and functional behavior separately, then correlate logs, events, commands, metrics, and configuration history. Treat the assumption that a valid change produces the wrong outcome because variables, permissions, mapping, or sequencing are incorrect as a hypothesis until a reproducible retest confirms the cause.

Validation Checklist

• The required configuration, permissions, sequence, connectivity, and functional behavior were checked and recorded.
• The normal path and a course-specific exception were tested.
• The ODF deployment design, storage-class catalog, workload tests, monitoring evidence, and recovery procedure 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 Storage Classes, Block, File, Object Services, and Workload Integration, explain the observed platform behavior, and support the result with a reviewable ODF deployment design, storage-class catalog, workload tests, monitoring evidence, and recovery procedure.