-
Epic
-
Resolution: Done
-
Blocker
-
None
-
None
This story is about the missing steps to complete the integration of BGP support for NextGen deployment, by fully leveraging the NextGen operators and config options.
There was already a way to deploy it but having many manual steps or configurations out of NextGen operators. The missing pieces are:
- configure spine leaf on CRC/OpenShift nodes
- configure spine leaf connection on the EDPM nodes
- configure loopback devices on the EDPM nodes
- configure FRR in the EDPM nodes
- (CI) adapting bgp-playground for this (e.g., changing the IPs on the leafs as overlapping IPs are not supported)
Note this relies on Network nodes for supporting tenant networks being exposed (due to limitations on sharing FRR with metallb in the openshift workers)
- depends on
-
OSPRH-2570 BGP OSP 18.0 Regression Testing and CI/Tooling Improvements
- Closed
- is blocked by
-
OSPRH-6932 Changes in initial rhoso18 BGP job required to run tests
- Closed
-
OSPRH-7813 Modify BGP DT01 to apply BGP at controlplane
- Closed
- is related to
-
OSPRH-652 Provisioning EDPM networker node
- Closed
- links to