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

• ControlPlaneMachineSet provides automation for scaling and otherwise reconfiguring the control plane machines within an openshift cluster. It allows an automated way to completely replace the control plane in a rolling update fashion.
• We currently don't support this on IBM cloud
• We need to define an API for the failure domain representation on IBM. This will likely look like the AWS one. The failure domain should capture the subset of fields in the IBM providerSpec that can vary between control plane machines.
• Once the APi is confirmed, an implementation in the CPMS repository will be needed in the machineproviders package to handle the provider specific parts of the interface .
• The nutanix PR https://github.com/openshift/cluster-control-plane-machine-set-operator/pull/258 should provide some guidance

Why is this important?

• …

Scenarios

1. ...

Acceptance Criteria

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

Dependencies (internal and external)

1. ...

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>