-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
ACM 2.11.0
-
None
-
Remove the core_woker label from the metric acm_managed_cluster_info
-
False
-
None
-
False
-
Not Selected
-
To Do
OCP/Telco Definition of Done
https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
Epic Template descriptions and documentation.
https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
ACM-wide Product Requirements (Top-level Epics)
https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit
*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*
Epic Goal
In ACM 2.11, we separated core_worker label from the metric acm_managed_cluster_info as a new metric acm_managed_cluster_worker_cores, which tracks the number of CPU cores on the worker nodes of the ACM managed clusters, the legacy metric label should be removed after a deprecation period.
- Comment from spasquie@redhat.com
I'd be in favor of removing the legacy metric eventually if there's no use for it. I'm not sure what's your policy around it though, maybe you want to have a deprecation period.
- Comment from sberens@redhat.com
I think we need to evaluate that further and not make any sudden move. I know our internal telemetry reports, which also then get compiled into dashboard views in Tableau (internal for RH use) make use of this existing metric. There may be other impacted areas as well, especially from customers as we have documented that metric for many releases now.In the least, if we need to move forward, it would require sufficient deprecation notice across 3 (minimum) releases, and, a suitable documented replacement.
More details can be found in the doc/comment of https://docs.google.com/document/d/1WbQyaY3C6MxfsebJrV_glX8YvqqzS5fwt3z8Z8SQ0VY/edit?usp=sharing.
Why is this important?
...
Scenarios
...
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 - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable.
