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

• Provide a mechanism to verify basic networking connectivity before deploying OpenShift in an environment.

Why is this important?

• Networking issues can result in non-obvious deployment failures. It would make debugging a lot easier if we could catch those in isolation before attempting to deploy the rest of the OpenShift components.

Scenarios

1. As an OpenShift deployer, I want to be able to confirm that my host networking is correctly configured before deploying OpenShift.
2. As an OpenShift deployer, I want to have all of the networking tools available to debug problems with host networking.

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. Is this a standalone process or a step in the regular deployment?
2. If part of the regular deployment, should it be optional or done as part of every deployment?

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>