Feature Overview

 
Provide support for the deployment and management of RHEL 9.6 based dataplane nodes for RHOSO 18. RHEL 9.6 provides support for new hardware including those needed for AI workloads. Providing this support allows customers to utilize RHOSO 18 to manage that hardware.

Goals

• Provide to customers an RHEL 9.6 based EDPM image for dataplane deployment and management.

Requirements (mandatory -_ Complete while in Refinement status):
A list of specific needs, capabilities, or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the Feature shifts. If a non MVP requirement slips, it does not shift the feature.

Done - Acceptance Criteria (mandatory - Complete while in Refinement status):
Acceptance Criteria articulates and defines the value proposition - what is required to meet the goal and intent of this Feature. The Acceptance Criteria provides a detailed definition of scope and the expected outcomes - from a users point of view

• RHEL 9.4 and 9.6 dataplane nodes can be deployed using RHOSO 18
• RHEL 9.4 and 9.6 dataplane nodes can be managed using RHOSO 18
• A RHEL 9.6 based EDPM image is available in the catalog

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):
Include use case diagrams, main success scenarios, alternative flow scenarios.

• Greenfield deployment on just 9.6 dataplane
• Brownfield deployment with 9.4 already deployed, adding 9.6 (assuming via availability zones)
• moving all existing computes from 9.4 to 9.6

Out of Scope _{}(Initial completion while in Refinement status):{_}
High-level list of items or persona’s that are out of scope.

• RHEL 9.5 support and support for RHEL versions greater than 9.6

Documentation Considerations _{}(Initial completion while in Refinement status):{_}
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation..

• Updates to the deployment and management guides will be needed to include RHEL 9.4 and RHEL 9.6 support.
   

Questions to Answer _{}(Initial completion while in Refinement status):{_}
Include a list of refinement / architectural questions that may need to be answered before coding can begin.

• What is the upgrade path from 9.4 to 9.6?  Do we support in-place or just scale-in/scale-out?

Background and Strategic Fit (Initial completion while in Refinement status):
Provide any additional context is needed to frame the feature.
<your text here>

Customer Considerations _{}(Initial completion while in Refinement status):{_}
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
<your text here>

Team Sign Off (Completion while in Planning status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

• …