Uploaded image for project: 'Network Hardware Enablement'
  1. Network Hardware Enablement
  2. NHE-252

setup CI in upstream ovn-kubernetes for MLX nics

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • None
    • None
    • CI in upstream ovn-kubernetes for DPU testing
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-481 - OpenShift Core Network Hardware enablement Improvements
    • OCPSTRAT-481OpenShift Core Network Hardware enablement Improvements
    • 100
    • 100% 100%
    • NHE Sprint 231, NHE Sprint 232

      Several hardware related features are enabled in ovn-kubernetes but not gated in upstream CI:

      1. OVS HWOL with plain NIC (e.g. CX-5, CX-6)
      2. OVS HWOL with DPU in plain NIC mode (e.g BlueField-2)
      3. 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

            sdaniele@redhat.com Salvatore Daniele
            zshi@redhat.com Zenghui Shi
            Jason Boxman Jason Boxman
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: