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 users to use Machines and MachineSets within OCP running on the Azure Stack Hub platform

Why is this important?

• Expanding support for new platforms for OCP

Scenarios

1. ...

Acceptance Criteria

• Expand existing Azure Machine API provider to support ASH or create new provider for ASH
• Ensure we have CI env access and set up MAO E2E suite against ASH implementation
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. Access to an ASH environment for development
2. UPI scripts for creating OCP cluster on ASH

Previous Work (Optional):

1. …

Open questions::

1. …

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>