[PERFSCALE-3433] Add BM CPT example

[josecastillolema]

Type of change

• Refactor
• New feature
• Bug fix
• Optimization
• Documentation Update

Description

New BM CPT example

Checklist before requesting a review

• I have performed a self-review of my code.
• If it is a core feature, I have added thorough tests.

Testing

$ orion cmd --config examples/metal-perfscale-cpt-node-density-heavy.yaml --lookback 15d --ack /usr/local/bin/orion_files/ack/4.18_cluster-density_ack.yaml --hunter-analyze
2025-01-08 14:30:26,583 - Orion      - INFO - file: orion.py - line: 125 - 🏹 Starting Orion in command-line mode
2025-01-08 14:30:26,592 - Orion      - INFO - file: utils.py - line: 218 - The test metal-perfscale-cpt-node-density.heavy has started
2025-01-08 14:30:26,593 - Matcher    - INFO - file: matcher.py - line: 65 - Executing query against index=perf_scale_ci-*
2025-01-08 14:30:27,091 - Matcher    - INFO - file: matcher.py - line: 65 - Executing query against index=ripsaw-kube-burner-*
2025-01-08 14:30:27,229 - Orion      - INFO - file: utils.py - line: 52 - Collecting podReadyLatency
2025-01-08 14:30:27,229 - Matcher    - INFO - file: matcher.py - line: 65 - Executing query against index=ripsaw-kube-burner-*                                             2025-01-08 14:30:27,360 - Orion      - INFO - file: utils.py - line: 52 - Collecting apiserverCPU
2025-01-08 14:30:27,360 - Matcher    - INFO - file: matcher.py - line: 65 - Executing query against index=ripsaw-kube-burner-*
2025-01-08 14:30:27,849 - Orion      - INFO - file: utils.py - line: 52 - Collecting multusCPU
2025-01-08 14:30:27,849 - Matcher    - INFO - file: matcher.py - line: 65 - Executing query against index=ripsaw-kube-burner-*
2025-01-08 14:30:28,123 - Orion      - INFO - file: utils.py - line: 52 - Collecting monitoringCPU
2025-01-08 14:30:28,123 - Matcher    - INFO - file: matcher.py - line: 65 - Executing query against index=ripsaw-kube-burner-*
2025-01-08 14:30:28,438 - Orion      - INFO - file: utils.py - line: 52 - Collecting ovnCPU
2025-01-08 14:30:28,438 - Matcher    - INFO - file: matcher.py - line: 65 - Executing query against index=ripsaw-kube-burner-*
2025-01-08 14:30:28,754 - Orion      - INFO - file: utils.py - line: 52 - Collecting etcdCPU
2025-01-08 14:30:28,754 - Matcher    - INFO - file: matcher.py - line: 65 - Executing query against index=ripsaw-kube-burner-*
2025-01-08 14:30:28,911 - Orion      - INFO - file: utils.py - line: 52 - Collecting etcdDisk
2025-01-08 14:30:28,911 - Matcher    - INFO - file: matcher.py - line: 65 - Executing query against index=ripsaw-kube-burner-*
2025-01-08 14:30:29,053 - Orion      - INFO - file: utils.py - line: 52 - Collecting kubelet
2025-01-08 14:30:29,053 - Matcher    - INFO - file: matcher.py - line: 65 - Executing query against index=ripsaw-kube-burner-*
metal-perfscale-cpt-node-density.heavy
======================================
time                       uuid                                  buildUrl                                                                                                                                                                                                                     podReadyLatency_P99    apiserverCPU_avg    multusCPU_avg    monitoringCPU_avg    ovnCPU_avg    etcdCPU_avg    etcdDisk_avg    kubelet_avg
-------------------------  ------------------------------------  -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------  ---------------------  ------------------  ---------------  -------------------  ------------  -------------  --------------  -------------
2025-01-07 14:46:44 +0000  f4e2222e-7815-436c-9fc9-6d3ff4b52a0c  https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/59744/rehearse-59744-periodic-ci-openshift-qe-ocp-qe-perfscale-ci-main-metal-4.17-latest-x86-weekly-6nodes/1876573559636103168                  40000             19.2083          1.54185              1.44461       3.44357         18.995      0.00129097        92.9906

[josecastillolema]

@jtaleric @vishnuchalla any idea why the CI test is failing?