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

• Investigate how NTO can provide node level tuning to the worker nodes in the hosted cluster
• Implement the design in which NTO can provide node level tuning to the worker nodes in the hosted cluster

Why is this important?

• NTO is a core operator in OpenShift. It managed the tuned profiles and the performance profiles (4.11+). We need to figure out how NTO can still operate in the restricted environment for the hosted cluster

Scenarios

1. Customer wants to change the node level tuning (like sysctls) on the hosted cluster worker nodes to get better performance for specific workloads

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. …

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>