Power Enterprise Pools 2.0 - Metered Usage Enhancements

Hi David,

For restricting partition level usage, you can use the partition level settings (Virtual Procs, Max seeting) and Shared proc pool level settings, if partitions are in shared processor pools. For charge back, there are APIs available which can be used to retrieve utilization information and some of the below mentioned use cases can be addressed using the utilization information based on use cases. Currently, there are no plans to have EP2.0 control Partition level usage with base or metered.

Thanks.

Hi David,

Currently, the concept of EP2.0 is sharing resources across a pool of systems and all the capacity/utilization is tracked at a pool level for metering purposes. So even though there is base capacity per system, its aggregated across the pool. So to restrict usage of base vs metered at a specific partition level would be a new model for Enterprise Pools. We will evaluate the request to see the possibilities.

Thanks.

Thanks.

Thanks for the feedback. I can see how these API's would be useful to automate & externalise the usage data. The issue however remains in that capacity is calculated at the Pool level, not at the partition level. With scale-up Power Systems we have the capacity to run 100's of partitions on a single physical system, we need usage data at the partition level.

The reporting was one part of this enhancement, the more important component of this RFE is to provide greater controls for base and metered capacity at the partition level. What is required is configuration options to enable a:

- Partition to only access base capacity
- Partition to only access metered capacity
- Partition to access both base & metered capacity (the current operating mode)

Will this require a fundamental change in the way EP 2.0 is currently designed?

Hi David,

For chargeback purposes, we have currently provided API's that can be used for retrieving utilization information for systems and lpars. You can add tags and group them based on the categories needed. Granular partition level control can still be done existing partition level settings as needed, but the base/metered capacity is calculated at a pool level currently. Please see if the below API's would help you for charge back purposes

https://ibmcmc.zendesk.com/hc/en-us/articles/4407128710803-GET-ep-usage-pools
https://ibmcmc.zendesk.com/hc/en-us/articles/4407136086291-GET-ep-inventory-tags
https://ibmcmc.zendesk.com/hc/en-us/articles/4407128689427-GET-ep-usage-tags

Thanks.

Having the functionality as identified in the 3 example use cases would be great for our business

These enhancements would align the PEP 2.0 Metered Usage to the real world use cases of PEP. We (as a BP) have the requirement from users to be able to provide chargeback to environments/projects that consume Credits.