-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
Design a Bare Metal VXLAN Integration MVP
-
False
-
-
False
-
-
Not Selected
-
?
-
?
-
To Do
-
RHOSSTRAT-1117 - Baremetal multitenancy using VTEP/VXLAN
-
?
-
rhos-ops-day1day2-hardprov
-
?
-
100% To Do, 0% In Progress, 0% Done
-
-
-
-
Critical
Goal:
- At a high level we need to work in the community to find a forward pattern to enable network Operators
- Rooted at this are issues with the interpretation and capabilities.
- Some want to extend vxlan natively – but OVN+OVS have broken models which are incompatible with physical gear.
- Bottom line, get a spec merged and enough of a clear plan so we can proceed in community context.
Acceptance Criteria:
- One or more merged specs which demonstrates an overall viable design which could enable physical
- Further implementation epics created as-needed based upon the shape and requirements.
- Odds are, we might not be able to natively support VXLAN port attachment in some cases, such as Cisco nexus fabrics utilizing centralized config. That should be a separate RFE/Rhosstrat item, but we first need to figure out the connection to before designing the end mechanism.
Open questions:
- It is presently unknown how "accepting" of the connectivity pillar may be to this modeling. Historically speaking, this is an area they don't quite relate to due to the network modeling as well, which has largely left the area in Hardware provisioning as it matches with the use case.