Feature Overview 

Complete the documentation required to support distributed control planes across low latency L3 interconnected data centers. The functionality was released in FR2.

Goals

• What is the difference between today’s current state and a world with this Feature?

Provide customer facing documentation about how to deploy and manage distributed control planes using a low latency L3 interconnected network between data centers. Must be published at https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/  

Requirements

Done

Guides cover the deployment and management of both distributed control plane nodes and distributed zones with multi-cells are completed and published to the RHOSO documentation area.

Out of Scope
High-level list of items or persona’s that are out of scope.
<your text here>

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..
<your text here>

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.
<your text here>

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

• …