-
Epic
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
None
-
CI in upstream ovn-kubernetes for DPU testing
-
BU Product Work
-
False
-
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-481 - OpenShift Core Network Hardware enablement Improvements
-
OCPSTRAT-481OpenShift Core Network Hardware enablement Improvements
-
0% To Do, 0% In Progress, 100% Done
-
NHE Sprint 231, NHE Sprint 232
Several hardware related features are enabled in ovn-kubernetes but not gated in upstream CI:
- OVS HWOL with plain NIC (e.g. CX-5, CX-6)
- OVS HWOL with DPU in plain NIC mode (e.g BlueField-2)
- OVS HWOL with DPU in Embedded CPU mode (e.g. BlueField-2)
To maintain the quality of hardware related feature in ovnk and avoid regressions introduced by adding/updating other ovnk features, we would want to setup a CI to continuously verify upstream changes against DPU deployment.
One example is the SR-IOV Operator upstream CI, third-party can hook up their CI test env with github PR and trigger the test through PR comment.
https://github.com/k8snetworkplumbingwg/sriov-network-operator/blob/master/ci/README.md