Uploaded image for project: 'OpenShift Network Plumbing'
  1. OpenShift Network Plumbing
  2. NP-639

Support for ovn-kubernetes to openshift-sdn CNI Migration

XMLWordPrintable

    • Support for ovn-kubernetes to openshift-sdn CNI Migration
    • BU Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • Green
    • In Progress
    • OCPSTRAT-365 - Support Enhancements for ovn-kubernetes to openshift-sdn CNI Migration
    • OCPSTRAT-365Support Enhancements for ovn-kubernetes to openshift-sdn CNI Migration
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      • Support the ability to migrate a cluster from the ovn-kubernetes CNI plugin to the openshift-sdn CNI plugin.

      Why is this important?

      • Customers that need to migrate from the default CNI plugin of OpenShift 4.12+ (ovn-kubernetes) to the older openshift-sdn CNI plugin is expected to be rare, but non-zero. The possibility exists that a long-time user of openshift-sdn will opt to install or migrate to ovn-kubernetes for its new features, and after some time of use, determine it necessary to go back to openshift-sdn, for whatever reason. This Epic adds support for that "reverse" migration, and builds upon the logic currently used for rollbacks during the already-supported openshift-sdn to ovn-kubernetes migration process.

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      DOD

      1. Reverse migration operates and has instructions for users, as well as full test coverage for CI & QE.

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. The rollback process already supported in openshift-sdn to ovn-kubernetes migrations.

      Open questions::

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

          There are no Sub-Tasks for this issue.

              pliurh Peng Liu
              mcurry@redhat.com Marc Curry
              Weibin Liang Weibin Liang
              Jason Boxman Jason Boxman
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: