Feature Overview (mandatory - Complete while in New status)

Define and test the adoption procedure for 17.1 DCN environments that are using ceph at the edge sites.

Goals (mandatory - Complete while in New status)

Today DCN 17.1 customers cannot adopt to RHOSO 18. This feature aims at providing a procedure to allow DCN with ceph at the edge to adopt RHOSO18.

Requirements

We can start with only one ceph scenario as the edge with TP.

Done - Acceptance Criteria and Use Case
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

1. Ability to adopt a 17.1 DCN with HCI-Ceph configuriation to RHOSO 18, following a documented and tested procedure

Out of Scope 

Non Ceph storage at the edge

Documentation Considerations

TP for now, will need to be included in the broader DCN adoption doc for fully supported release

Questions to Answer

• Can we confirm the target customers specific configuration?

Background and Strategic Fit 

We need to bring customers on the supported DCN deployment feature forward to RHOSO-18

Customer Considerations 

See Links, we have at least one specific target customer that requires this feature to move forward on a target schedule

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

• …