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

• Add mechanism to allow for group configuration of nodes (e.g. two configurations - one for masters, one for workers).

Why is this important?

• Many network layouts do not require per-node configurations, and it's clunky to require a single configuration to be copy-pasted to many node definitions. It's also potentially error-prone because duplicate copies of the same data may accidentally drift.

Scenarios

1. As a deployer, I want to deploy one set of VLANs on all of my master nodes, and a different set on all of my worker nodes.
2. As a deployer, I want to deploy a single provision-time configuration to all of the nodes in my cluster.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• It must be possible to deploy a single configuration across multiple nodes, ideally with the ability to apply them to only a subset of nodes.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. https://github.com/openshift/enhancements/pull/817

Open questions::

1. What level of granularity do we need to support? All nodes, masters and workers, arbitrary subsets?

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>