XML

Word

Printable

Type: Story
Resolution: Done
Priority: Major
Fix Version/s: openshift-4.14, July Release for PSAP - IV, July Release for PSAP - V, July Release for PSAP - VI, July Release for PSAP - VII, July Release for PSAP - VIII
Affects Version/s: None
Component/s: NTO
Labels:
- NTO

Work Type:
Proactive Architecture
Epic Link:
4.14: Address the technical debt carried from previous NTO releases
Ready:
False
Blocked:
False
Blocked Reason:
None

<--- Cut-n-Paste the entire contents of this description into your new Epic --->

Epic Goal

NTO/PAO is the consumer of TuneD released via the Fast Datapath. While the FDP TuneD releases go through the automated TuneD testing, NTO/PAO have their own tests that need to pass too before TuneD is deemed fit to be used in OCP. Failures to do so, result in issues such as these. We need to make sure new TuneD FDP releases containing new functionality have no regressions breaking NTO/PAO.

Why is this important?

While NTO/PAO have their own nightly testing, catching issues with TuneD at this stage is too late. We need to catch these issues before they propagate into OCP.

CI - MUST be running successfully with tests automated
Release Technical Enablement - Provide necessary release enablement details and documents.
...

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>