-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
5
-
False
-
-
True
-
-
ACM will be a metered offering that is measured via openshift observatorium
SKU: MW02023HR
platform: OpenShift
product_tag: rhacm
recording rule: acm_capacity_effective_cpu_cores:sum
awsDimension: acm_vcpu_hours
no billing factor multiplier
prepaid contracts are enabled
could be on top of ROSA Classic or ROSA HCP
There is a long-running test cluster that the ACM team uses with an instance id of "3cb2bdd7-0471-40cf-b54f-c9924a296150" that we've been using to validate with them.
WIP branch: https://github.com/RedHatInsights/rhsm-subscriptions/compare/main...lburnett/SWATCH-33391-acm-config
Acceptance Criteria:
- create swatch-product-configuration yaml file for ACM. it should use the same template and productLabel regex as ROSA
- verify the outputs of the promql generator in swatchdog
poetry run swatchdog prometheus promql --source ~/code/rhsm-subscriptions/swatch-metrics/src/main/resources/application.yaml --product-config-dir ~/code/rhsm-subscriptions/swatch-product-configuration/src/main/resources/subscription_configs --product rhacm
- Component Tests
- should be able to parameterize any of the tests that include ROSA, note that ROSA has a billingFactor for one of its metrics and ACM doesn't. So there might be asserts that need to be adjusted (or can't parameterize that test and just need to write a new one).
- Integration Ephemeral Tests
- Tally -> Billable Usage
- swatch-producer-aws -> moto
- blocks
-
SWATCH-3512 [GUI] RHACM boilerplate
-
- Closed
-
- is related to
-
SWATCH-3543 Set Up Longrun Test for RHACM
-
- Closed
-
- mentioned on