tree 03da12d74bb82812da80249956c9087e619c502f
parent 3c212f087b0b50c49a59d60200259b1adced25dd
author Gunnar Mills <gmills@us.ibm.com> 1631735236 -0500
committer Gunnar Mills <gmills@us.ibm.com> 1632156781 +0000

meta-ibm: Redfish: Enable new power/thermal

After over a year of discussion, Redfish released new power and thermal
schemas as part of the Redfish 2020.4 release.

These new powersubsystem, thermalsubsystem, fan, powersupply, etc
schemas can co-exist with the old power and thermal schemas.

The old schemas and the new schemas are controlled by different options.

The current plan for bmcweb is:
1. Until the new schemas are all in and tested, as a default, enable the
   old schemas and disable the new.
2. After the new have been in and tested, enable them. This means the
   old and new will co-exist if running the defaults. The sensor
   collection behavior will reflect the new schemas, that is all sensors
   can be found under the sensor collection.
3. After an OpenBMC release, at a later time, disable the old and add
   appropriate deprecation.

This change here, enabling the new schemas, jumps meta-ibm to #2.
This reflects our desire for our Redfish clients to start using the new
schemas.

Some reasons why the ThermalSubsystem/PowerSubsystem are an improvement
on the existing Thermal/Power schemas:
1. They include the latest properties like LocationIndicatorActive.
2. Fans, PowerSupplies, Temperatures were arrays in the old schemas.
   This was cumbersome and could hit limits of JSON arrays.
3. Large amount of static data mixed with sensor readings, which hurt
   performance in certain cases.
4. Inconsistent definitions of properties vs newer schemas like Processor
   and Memory schemas.

Reference:
https://www.dmtf.org/sites/default/files/standards/documents/DSP0268_2020.4.pdf

Tested: Built bmcweb. See the new sensor behavior.

Change-Id: I9a698cbc162a331c21c7dc5138000faac6247f9b
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>