Uploaded image for project: 'On Prem Networking'
  1. On Prem Networking
  2. OPNET-282

Tech preview implementation of configure-ovs alternative

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • Implementation of configure-ovs alternative
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • To Do
    • OCPSTRAT-439 - Support of configure-ovs Alternative
    • OCPSTRAT-439Support of configure-ovs Alternative
    • 47
    • 47% 47%
    • Hide

      [QE]Apr 29, 2024 pre-merge testing, testing modify configuration of br-ex day2 with knmstate and scale up

      [QE]Apr 11, 2024 pre-merge testing, testing modify configuration of br-ex day2 with knmstate

      [QE]Apr 7, 2024

      • Pre-merge testing OPNET-386 install cluster with draft PR on RDU2 successfully, apply nncp to copy config to day2 failed, nncp is in Progressing and lost the node. 

      [QE]Mar 28, 2024

      • Pre-merge testing OPNET-386 install cluster with draft PR on RDU2, meet issue on the bootstrap host, debugging

      [QE]Mar 21, 2024

      • Pre-merge testing OPNET-386 blocked due to unavailability of 4.16 accepted nightly.

       [QE]Mar 14, 2024

      Show
      [QE] Apr 29, 2024 pre-merge testing, testing modify configuration of br-ex day2 with knmstate and scale up [QE] Apr 11, 2024 pre-merge testing, testing modify configuration of br-ex day2 with knmstate [QE] Apr 7, 2024 Pre-merge testing  OPNET-386 install cluster with draft PR on RDU2 successfully, apply nncp to copy config to day2 failed, nncp is in Progressing and lost the node.  [QE] Mar 28, 2024 Pre-merge testing  OPNET-386 install cluster with draft PR on RDU2, meet issue on the bootstrap host, debugging [QE] Mar 21, 2024 Pre-merge testing  OPNET-386 blocked due to unavailability of 4.16 accepted nightly.   [QE] Mar 14, 2024 Draft PR available machine-config-operator/pull/4249   Pre-merge testing  OPNET-386 planned for Sprint 251 starting Monday.

      This is the followup epic to https://issues.redhat.com/browse/OPNET-265 Once we have an approved enhancement (which we expect to be a significant piece of work in itself), this will track the implementation. We expect this to happen in 4.15 or later unless things go very smoothly with the enhancement epic in 4.14.

            bnemec@redhat.com Benjamin Nemec
            bnemec@redhat.com Benjamin Nemec
            Qiong Wang Qiong Wang
            Darragh Fitzmaurice Darragh Fitzmaurice
            Votes:
            1 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated: