OCP/Telco Definition of Done
Epic Template descriptions and documentation.

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

Epic Goal

• Enable use of OSUS for OSD/ROSA upgrade scheduling by providing OCM/CS status from CVO as provided in ClusterVersion status.

Why is this important?

• OSD and ROSA Classic (not HCP) today use old ClusterImageSet CRs to manage available upgrade metadata for upgrade scheduling.  This does not take into account any cluster specific configuraiton or conditional edges.  Impact to user experience in the form of upgrade edges being removed, resulting in scheduled upgrades being cancelled.

Scenarios

1. See "why".

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• SD confirms OCM / CS has sufficent information for upgrade scheduling to stop using ClusterImageSets.

Dependencies (internal and external)

1. Service Delivery OCM team.

Previous Work (Optional):

1. Hypershift: https://github.com/openshift/hypershift/pull/1954/files#diff-7f610a19967d28b69fe2496bbbe249ef131c9c3d5419fa3a830b3f931f2bb242R1813-R1832 

Open questions::

1. none?

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>