Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-141445

add option for NMState to manage OVS flows using API

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • nmstate
    • None
    • None
    • rhel-net-mgmt
    • 3
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Hide

      Definition of Done:

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) The acceptance criteria defined below are met.

      Given an OVS bridge "br-mesh" with external flows added via ovs-ofctl,

      When nmstate applies a policy that modifies the bridge MTU (but not flows),

      Then the external flows with cookie 0x1 remain intact on "br-mesh"
      –
      Given an OVS bridge "br-mesh" with external flows (cookie=0x1)
      And the bridge has port "eth1" attached

      When nmstate applies a policy that adds a new port "eth2" to the bridge

      Then the external flows with cookie 0x1 remain intact and the new port "eth2" is successfully added.

      ( ) Integration test case is available upstream.

      ( ) Code is reviewed and merged upstream.

      ( ) Preliminary testing is done.

      ( ) Upstream documentation is written in the upstream MR.

      ( ) Release notes text is written in the RHEL issue.

      ( ) A demo is recorded

      Show
      Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. Given an OVS bridge "br-mesh" with external flows added via ovs-ofctl, When nmstate applies a policy that modifies the bridge MTU (but not flows), Then the external flows with cookie 0x1 remain intact on "br-mesh" – Given an OVS bridge "br-mesh" with external flows (cookie=0x1) And the bridge has port "eth1" attached When nmstate applies a policy that adds a new port "eth2" to the bridge Then the external flows with cookie 0x1 remain intact and the new port "eth2" is successfully added. ( ) Integration test case is available upstream. ( ) Code is reviewed and merged upstream. ( ) Preliminary testing is done. ( ) Upstream documentation is written in the upstream MR. ( ) Release notes text is written in the RHEL issue. ( ) A demo is recorded
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      Background:  There is a growing need to add additional ovs flows for the configuration of certain networking configurations.  This specific ask comes around the requirements for Spectrum-X from NVIDIA.

      Description: Please add option for NMState to manage OVS flows using API. Currently we use shell scripts and systemd with Machine Config to do this.

              nm-team Network Management Team
              rh-ee-sdambo Shinel Dambo
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: