Red Hat SummitEste contenido no está disponible en el idioma seleccionado.
Chapter 2. April 2025
2.1. Cluster-hour cost
You can use a new cost model metric, cluster-hour`, to better model the hourly cost of operating your entire cluster. This metric adds additional hourly costs of each of your clusters to your overall cost. You can distribute costs based on either actual CPU, or memory usage, which ensures that workloads are proportionately charged based on the resources that they consume.
To view all metrics, see Cost model metrics.
2.2. Oracle is no longer supported
Oracle Cloud is no longer a supported cloud provider for cost management integrations.
2.3. New metrics for OpenShift subscription-based costs
There are hidden costs associated with running an OpenShift cluster. Many of these costs are from subscriptions related to CPU core metrics.
To better capture these costs and distribute them to user projects, cost models have new metrics. To view the metrics, see Cost model metrics.
2.4. Updates to Virtual Machines (VMs)
Cost management made several enhancements that are related to VMs:
Distribute platform cost to OCP VMs
To more accurately allocate costs, users can now distribute platform, unallocated capacity, network, and storage costs to VMs. To provide a more granular chargeback model and ensure that shared expenses are allocated according to each VM’s consumption, this enhancement uses CPU and memory consumption to proportionally distribute costs.
Cost model per VM count metrics
Cost management added a new cost model metric for OpenShift Virtualization VMs which enable users to apply charges based on the number of VMs running in a cluster. This metric supports both "per VM per month" and "per VM per hour" pricing in cost models. This enhancement offers a more flexible approach to track and charge VM usage.
Storage support for virtual machines
Users can track costs that are directly associated with running a VM on Red Hat OpenShift Virtualization. Initially, users could only track costs related to CPU and memory resources. Now, the aggregated monthly total cost includes the cost of storage that running VMs use. The endpoint /api/cost-management/v1/reports/openshift/resources/virtual-machines/ returns information about the storage that is associated with the VM. For example storageclass, capacity,usage, units, and persistentvolumeclaim(PVC) name.
When multiple VMs share storage, the storage costs are attributed to only one of the VMs. A planned enhancement will distribute the cost across all the attached VMs.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}