-
Epic
-
Resolution: Obsolete
-
Major
-
None
-
openshift-4.12
-
ConnectX-6 Dx OVS hardware offload with TC in ovn-k8s
-
False
-
-
False
-
Not Selected
-
To Do
-
Impediment
-
QE Needed, Docs Needed, TE Needed, PX Needed, Customer Facing
This work is only for CX6-DX. Even though Bluefield-2 embeds an CX6-DX, it should not be confused with the work in this story. This story is very similar to CX-5 offload, except that there are more flows that can be offloaded. The tool https://github.com/Billy99/ovn-kuber-traffic-flow-tests can check if flows would fail after offloading. We also need to ensure that those flows are actually offloaded. CI jobs should also be added.
1) Get a CX-6 DX NIC (so not a BF-2 with CX-6) to do manual testing first. Verify the flows as described above. NOTE: It is actually better to test with non-bluefield to remove a layer of complexity as well historically with/without bluefield has an impact on the results.
2) After manual testing of the flows are done, it is recommended to create Jenkins CI for this.
Scenarios
- x86 OpenShift host using TC offoad with ConnectX-6 Dx NIC
- clones
-
NHE-3 [tech-preview] ConnectX-6 Dx OVS hardware offload with TC in ovn-k8s
- Closed