|
|
Post by ueliyahu on Sept 20, 2023 17:01:17 GMT
Hi,
I'm currently trying to understand how to utilize the PowerSubsystem scheme for power capping,
essentially configuring the system's power level.
I've observed that all the properties are read-only (RO), which means users cannot effectively make any changes
Power schema is in the process of being deprecated, yet there doesn't seem to be a replacement for these properties within the new Power Subsystem schema.
Could someone please provide some clarity on this matter?
Thanks
|
|
|
|
Post by jautor on Sept 20, 2023 19:23:52 GMT
The "power capping" function is found in EnvironmentMetrics in the new model, as "PowerLimitWatts". That property is a schema excerpt of a Control if you want to provide more details and metadata behind that value. This method allows a "cap" to be supported on either the Chassis, or on an individual component, such as a CPU/GPU, using the same definition.
For a Chassis, that instance would be located at: /redfish/v1/Chassis/{Chassis ID}/EnvironmentMetrics
This was added in the 2021.2 release, after the PowerSubystem models were released in 2020.4. We also added an "OperatingSpeedRangeMHz" control (in Processor and Memory) at that time, to allow support of both power-based and speed-based limiting.
Jeff
|
|
|
|
Post by ueliyahu on Sept 26, 2023 12:03:26 GMT
Thank you!
I examined the PowerLimitWatts parameter within the EnvironmentMetrics, and I also discovered that a similar feature is available within the Control scheme,
located at /redfish/v1/Chassis/{ChassisId}/Controls/{ControlId}.
What distinguishes these two options?
I am currently interested in implementing power capping functionality for a DPU card, but I'm uncertain which of these schemes is the appropriate one to use.
Thanks !
|
|
|
|
Post by mraineri on Sept 26, 2023 13:36:53 GMT
EnvironmentMetrics is the well-known path to specifically control the power limit on the chassis, whereas Control is the source of the data. So, a user performing this management via EnvironmentMetrics can be 100% certain that it's the setting for the power limit of the Chassis. The open-ended Controls collection allows an implementer to surface any controls they need to, but clients will likely have some difficulty mapping specific controls to underlying functionality in the system.
If you implement the EnvironmentMetrics view of things as well as Control, EnvironmentMetrics will point to the underlying Control resource as the source of data.
|
|
