-
Epic
-
Resolution: Duplicate
-
Normal
-
None
-
None
-
None
-
Ability to assign custom name formats to Control Plane Machines via CPMS
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-1418 - Allow Custom machine names when using the CPMS feature
-
OCPSTRAT-1418Allow Custom machine names when using the CPMS feature
-
100% To Do, 0% In Progress, 0% Done
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 new field to the CPMS that allows to define a Machine name prefix
- This prefix will supersede the current usage of the control plane label and role combination we use today
- The names must still continue to be suffixed with
<chars><idx> as this is important to the operation of CPMS
Why is this important?
- …
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
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>