XML

Word

Printable

<--- Cut-n-Paste the entire contents of this description into your new Epic --->

Epic Goal

The service delivery (SD) team (managed openshift services ARO, OSD, ROSA) would like to consolidate behind OVN as the future SDN solution in order to track OCP team's goals. To do so, SD need a way to migrate our managed fleet in a way that is no more impactful to the customer's workloads than an OCP upgrade, and that can be done at scale, in a safe, automated way that can be made self-service and not require SD to negotiate maintenance windows with customers.
We envision a tickbox in OCM that lets a customer initiate a self-service migration to OVN

Why is this important?

For efficiency and quality of support from SRE team to our customers, we would like to avoid as much as possible, bifurcating the managed OCP fleet between two SDNs.
There are ~1000 managed clusters today that run openshift-sdn. If we have a migration tool that fits our needs, we could reduce that number and, combined with making OVN our default for new clusters in the future, set an aspirational goal to eliminate openshift-sdn from the managed fleet entirely.

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

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>