-
Epic
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
Optimize monitoring stack CPU usage on single node openshift
-
False
-
False
-
NEW
-
To Do
-
TELCOSTRAT-87 - Single Core CPU CaaS Budget for DU Deployment w/ Single-Node OpenShift on Sapphire Rapids Platform
-
NEW
-
0
-
0%
-
Undefined
-
Telco 5G RAN
-
0
Epic Goal
- The overall goal is to fit all platform components into 1 core (2 HTs, 2 CPUs) for single node openshift deployments. The monitoring stack is one of the largest cpu consumers on single node openshift consuming ~ 200 mc at steady state, primarilty prometheus and the node exporter. This EPIC would track optimizations to the monitoring stack to reduce this usage as much as possible. Two items to be explored:
- Reduceing the scrape interval
- Reducing the number of series to be scraped
Why is this important?
- One of the key use cases for SNO is the RAN DU. A solution that maximizes the CPU footprint for the application workloads is key is a key portion of the end customer's business case.
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>