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

• Create a reproducible Environment Guidance that can be reused by QE for setting up manual Measurement Environments to track the 1C target. It should be inspired by the Telco Workload being reworked in https://issues.redhat.com/browse/CNF-10711
• Create an Effort together with QE to integrate 1C target measurement into the Telco KPI Pipelines to continously have it included in reports on current releases
• Create a set of reference KPIs that are documented to showcase how we measure the 1C Control Plane target and when we consider it done.

Why is this important?

• The 1C Target likely will have to be tracked over multiple releases and we need a reproducible environment together with a set of measurements that can be retriggered for every release to continously drive analysis and reporting for the Initiative
• When we calculate our next moves for the Initiative of coming closer to 1C we need numbers which can clearly deduce that our work is succeeding and gives us insight into what we need to tackle next
• We need to continously control that we observe no regressions for the 1C target.

Scenarios

1. vDU deployed for various Customers with a specific hardware profile found in the Telco Labs
2. 1C target usage for a reduced Control Plane scenario

For further guidelines or existing measurements, please reference the Test Plan in https://docs.google.com/document/d/1wSbxdFpmqqwDSHDjLmdCuQy1DjWGuQaMuO0Gp2SJQl0/edit?usp=sharing 

Acceptance Criteria

• Environment KPIs and Guide must be created and sustainable maintained in a Knowledge source of Edge Enablement that is shareable with other OCP Teams
• Release Technical Enablement - Documentation for the KPIs included must be present and there must have been an upskilling on these in Edge Enablement
• For every Release we need to be able to produce a report on the 1C target without investing again into researching methodology, so they need to be automatable
• The measurement methodology should be accompanied by a small Runbook on how to reproduce the measurements and in which environment they should be run
• The measurements should be based on prometheus metric reports ideally accompanied with a custom process metrics recorder such as https://github.com/Avielyo10/prom/ as much as possible to make later integration easier
• The metrics / KPIs should follow best practices and need to be explained so that its easier to reason why they are necessary when using them as action indicators for other core teams in openshift.
• The metrics / KPIs should be collectable in one sweep of prometheus so that we can integrate them into Scripts and CI later

Dependencies (internal and external)

• The baseline measurement and methodology needs to define which operators are included in the vDU core, and which optional operators should be considered overhead over the 1C goal. This has to be aligned with the various Telco Teams

Open questions::

• How will the Reporting be generated? Must be identified after Telco Pipeline is verified and has resulting KPIs

Done Checklist

• DEV - Environment KPIs and Guide: <link to meaningful PR or GitHub Issue>
• DEV - Measurement Methodology / Test Plan: <link to meaningful PR or GitHub Issue>
• DEV - Edge Enablement Upskilling: <link to Presentation / Recording>