Details
-
Epic
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
Identify metrics for indicating optimal node resource usage
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-154 - Create metrics, prometheus queries, dashboard in openshift that customer can monitor to understand their pod scaling limit
-
OCPSTRAT-154Create metrics, prometheus queries, dashboard in openshift that customer can monitor to understand their pod scaling limit
-
100
-
100%
Description
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
- To come up with set of metrics that indicate optimal node resource usage.
Why is this important?
- These metrics will help customers to understand the capacity they have instead of restricting themselves to hard coded max pod limit.
Scenarios
- As a owner of extremely high capacity machine, I want to be able to deploy as many pods as my machine can handle.
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- None
Previous Work (Optional):
Open questions::
- The challenging part is come up with set of metrics that accurately indicate system resource usage.
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>