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

• This is a requirement coming from an OpenStack customer, but because it impacts the on-prem networking components we are likely going to be involved.
• I'm opening this epic mostly so we don't lose track of this in our planning.
• https://issues.redhat.com/browse/OSASINFRA-2999 Marking as RED Because this epic is no longer the one that's tracking – the epic below, 3069 is. 

This epic: https://issues.redhat.com/browse/OSASINFRA-3069

Why is this important?

• Customers want to run their control plane nodes in multiple failure domains, one aspect of which is that they need to be on different subnets.

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>