Uploaded image for project: 'OpenShift SDN'
  1. OpenShift SDN
  2. SDN-4467

Alignment of FDP releases with OCP releases

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • openshift-4.16
    • None
    • None
    • Alignment of FDP releases with OCP releases
    • False
    • None
    • False
    • Not Selected
    • To Do
    • 0% To Do, 0% In Progress, 100% Done
    • Hide

      [QE] Jun 25, 2024 - Pending tasks captured in 4.17 Epic SDN-5032. State change to RELEASE PENDING.

      [QE] May 29, 2024 (Sprint 254)

      CI Workflow merged.

      QE test tagging will be undertaken this sprint.

      [QE] May 17, 2024 (Sprint 253)

      CI workflow reviewed by QE productivity team and is successfully executing the tagged tests.

      All the tagged cucushift and ginkgo E2E tests are executed.

      [QE] May 13. 2024 Successfully executed the CI workflow first round.

      https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/51675/rehearse-51675-pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-fdp-qe/1788830660220162048

      Two test cases failing

      https://issues.redhat.com/browse/OCPQE-21413 (OCP-70294) There were changes in port group that needs test script fix.

      Second test is environmental as test succeeded on rerun

       

      Scenario: OCP-18535:SDN should not show "No such device" message when run "ovs-vsctl show" command # features/networking/sdn.feature:210 waiting for operation up to 3600 seconds..
1 scenario (1 passed) 9 steps (9 passed) 0m47.245s

      [QE] May 5, 2024

      Tagging the test to determine the test set for validating the OVN/OVS rpms underway.

      Draft of validation plan https://docs.google.com/document/d/1D1cajLkOfYMkrbQGjmUF8FNaEaJpmPSKOvdshoxdZDw/edit

      CI workflow is being worked on.

      Show
      [QE] Jun 25, 2024 - Pending tasks captured in 4.17 Epic SDN-5032 . State change to RELEASE PENDING. [QE] May 29, 2024 (Sprint 254) CI Workflow merged. QE test tagging will be undertaken this sprint. [QE] May 17, 2024 (Sprint 253) CI workflow reviewed by QE productivity team and is successfully executing the tagged tests. All the tagged cucushift and ginkgo E2E tests are executed. [QE] May 13. 2024 Successfully executed the CI workflow first round. https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/51675/rehearse-51675-pull-ci-openshift-ovn-kubernetes-master-e2e-aws-ovn-fdp-qe/1788830660220162048 Two test cases failing https: //issues.redhat.com/browse/OCPQE-21413 (OCP-70294) There were changes in port group that needs test script fix. Second test is environmental as test succeeded on rerun   Scenario: OCP-18535:SDN should not show "No such device" message when run "ovs-vsctl show" command # features/networking/sdn.feature:210 waiting for operation up to 3600 seconds.. 1 scenario (1 passed) 9 steps (9 passed) 0m47.245s [QE] May 5, 2024 Tagging the test to determine the test set for validating the OVN/OVS rpms underway. Draft of validation plan https://docs.google.com/document/d/1D1cajLkOfYMkrbQGjmUF8FNaEaJpmPSKOvdshoxdZDw/edit CI workflow is being worked on.
    • ---
    • 0
    • 0

      Starting OpenShift 4.16, we will be required to support each OCP release for 36 months. That implies at any point in time, we will have about 9 releases to maintain. In OpenShift Networking, various teams are working on figuring out how to reduce our maintenance cost for the codebase. OCP uses OVN-Kubernetes as the default CNI which in turn uses OVN as the underlying networking platform. So far the OVN-Kubernetes downstream has been using specially tagged OVN rpms and consuming them from brew. There is an overall desire to consume OVN as a platform by moving to a model that is more idiomatic for the platform - i.e. consume OVN packages via FDP releases.

      Epic Goal

      This epic is intended to capture the work required to introduce representative OCP test cases in the release process for FDP to gate OVN releases

      Additional info

      Share test cases from OVN QE to understand any delta between how OVN QE tests vs OCP QE (OCP QE will share as well)

      Planning Done Checklist

      The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

      • Priority+ is set by engineering
      • Epic must be Linked to a +Parent Feature
      • Target version+ must be set
      • Assignee+ must be set
      • (Enhancement Proposal is Implementable
      • (No outstanding questions about major work breakdown
      • (Are all Stakeholders known? Have they all been notified about this item?
      • Does this epic affect SD? {}Have they been notified{+}? (View plan definition for current suggested assignee)
        1. Please use the "Discussion Needed: Service Delivery Architecture Overview" checkbox to facilitate the conversation with SD Architects. The SD architecture team monitors this checkbox which should then spur the conversation between SD and epic stakeholders. Once the conversation has occurred, uncheck the "Discussion Needed: Service Delivery Architecture Overview" checkbox and record the outcome of the discussion in the epic description here.
        2. The guidance here is that unless it is very clear that your epic doesn't have any managed services impact, default to use the Discussion Needed checkbox to facilitate that conversation.

      Additional information on each of the above items can be found here: Networking Definition of Planned

       

              zshi@redhat.com Zenghui Shi
              zshi@redhat.com Zenghui Shi
              Arti Sood Arti Sood
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: