Loading...

XML

Word

Printable

Type: Epic
Resolution: Unresolved
Priority: Critical
Fix Version/s: rhos-18.0 FR 2 (Mar 2025)
Affects Version/s: None
Component/s: internal
Labels:
None

Epic Name:
Spine/Leaf enablement
Story Points:
16.5
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Dev Approval:
Committed
Docs Approval:
No Docs Impact
Epic Status:
To Do
Feature Link:
RHOSSTRAT-77 - Support Distributed ctlplane nodes across low latency L3 interconnected DataCenters
PM Approval:
Proposed
QE Approval:
Committed
Hierarchy Progress Bar:

0% To Do, 10% In Progress, 90% Done
Intelligence Requested:
Market:

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

This epic tracks all the related issues for ensuring feature parity for Spine/Leaf in RHOSO18 with OSP17.

This is a nice to have based on the Feature description, included below for reference.
"Nice to have / Streached Goal successful deployment orchestrated by the openstack meta operator based on a spine-leaf network topology and routed provider networks"

blocks

OSPRH-1484 As a cloud operator, i want to adopt a spine and leaf deployment.

Backlog

OSPRH-2627 How to deploy dataplane nodes using BMO in Spine-and-Leaf architecture

Testing

is depended on by

OSPRH-5504 Pure L3 spine&leaf

In Progress

is triggering

OSPRH-11036 Create integration job deploying spine-and-leaf with Metal3

In Progress

relates to

OSPRH-2987 DHCP Relays support in the environment with Neutron DHCP Agents

Dev Complete

Assignee:: Harald Jensas

Reporter:: James Slagle

Team:: rhos-dfg-hardprov

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Created:: 2024/01/09 8:16 PM

Updated:: 2024/12/16 1:37 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates

PagerDuty