-
Epic
-
Resolution: Done
-
Blocker
-
None
-
Reduce ACM Agent footprint on SNOs for RAN Edge Deployments
-
False
-
None
-
False
-
Green
-
To Do
-
TELCOSTRAT-87 - Single Core CPU CaaS Budget for DU Deployment w/ Single-Node OpenShift on Sapphire Rapids Platform
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
Our goal is to help to create capacity & sizing recommendations for ACM.
Why is this important?
Customers need this type of capacity and sizing information as they embark on ACM deployments.
Scenarios
- Existing (brown-field) set up: ACM hub is running with real clusters being managed under it
- No ACM running (green-field) but clusters that would be managed exists
- No ACM running (green-field) and clusters that would be managed do not exist
Acceptance Criteria
...
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>
- relates to
-
-
- Closed
-