-
Initiative
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
Not Selected
-
False
-
False
-
-
0
-
0
-
rhos-connectivity-nfv
Feature Overview
A Tier 1 telco customer has expressed interest in support of SRv6, BGP, and IGP protocols such as ISIS on a compute node for OCP and RHOSO. Although the immediate request is from a specific customer, the capability benefits and will be positioned for other customers with similar needs.
Moving the mentioned functionality for the control plane and data plane from ToR to the compute node helps customers realize savings in both CAPEX and OPEX.
- CAPEX savings by moving ToR functionality to compute / worker nodes
- Expensive ToR switches (50k+), additional license costs for BGP, BGP, SRv6 etc
- OPEX savings
- Workload network configuration/services independent of network fabric configuration
- Workload migration without changing the fabric configuration
Support for OCP is a higher priority and will serve as a template for supporting OpenStack subsequently.
The grout project worked by the RHOSO NFV team supports the desired control plane functionality via FRR and a DPDK data plane meets the customers' requirements.
However, Grout does not have the desired network plumbing or enablement for OpenShift.
Open PE router has integration with Openshift and is the appropriate vehicle for delivering the grout functionality for Openshift.
This feature is intended to provide integration between Grout and the Open PE router, ultimately enabling Grout functionality with OpenShift and subsequently on RHOSO.
Goals
- Integration of grout with Open PE router
- Enablement of grout functionality for Openshift and Openstack
- Target is to deliver a day 2 operation functionality for POC purposes.
Requirements
| Requirement | Notes | isMVP? |
|---|---|---|
| Integration of grout with Open PE router to provide SDN and routing capabilities on control plane, such as SRv6, BGP, BFD, ISIS, possibly PCEP with DPDK data plane | yes | |
| Day 2 deployment enablement on OCP | yes | |
Done /Acceptance Criteria
- Operational functionality of Grout + FRR with Open PE router viding SDN + routing ca capability with a DPDK data plane
Out of Scope
- QE and official documentation is required
- Performance testing or benchmarking is required
Documentation Considerations
- Engineering document on how to deploy/install and configure grout with OCP
Questions to Answer
- Feasibility to support grout on OCP
- Identify and document any usability or functional challenges and gaps
Background and Strategic Fit
GA will pave the path to provide functionality to OCP and RHOSO customers to help achieve significant CAPEX and OPEX savings. This increases the value Red Hat provides to customers and helps with strengthening and growing the market share with the key differentiator in the value proposition.
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
| Reviewed By | Team Name | Accepted | Notes |
- …