diff options
author | Xiaochao Ma <maxiaochao@inspur.com> | 2021-03-02 10:53:13 +0300 |
---|---|---|
committer | Ed Tanous <ed@tanous.net> | 2022-08-01 17:09:26 +0300 |
commit | 2973963e3624872300c199e467b960ce4c4f3b29 (patch) | |
tree | 0336e242bcf5b62c41169af835520ca14801b336 /Redfish.md | |
parent | 4c7d4d33a7c5697460f4bc57015551f599fc6f54 (diff) | |
download | bmcweb-2973963e3624872300c199e467b960ce4c4f3b29.tar.xz |
Add Redfish ThermalSubsystem schema in bmcweb
The ThermalSubsystem is a new resource in Redfish version 2020.4.
It is a root for fans and temperatures. Fans are a new schema.
Temperature sensors will be part of the new ThermalMetrics schema.
ThermalSubsystem can co-exist with the current Thermal resource.
You can also control compilation through flags.
ThermalSubsystem is an improvement on the existing Thermal schema
because
1. It includes the latest properties like LocationIndicatorActive
2. Fans and Temperatures were arrays in the old Thermal schema and
this was cumbersome and could hit limits of JSON arrays
3. Large amount of static data mixed with sensor readings, which
hurt performance
4. Inconsistent definitions of properties vs like Processor and
Memory schemas
In a future commits Fans and ThermalMetrics will be added soon.
Reference:
https://www.dmtf.org/sites/default/files/standards/documents/DSP0268_2020.4.pdf
https://redfish.dmtf.org/schemas/v1/ThermalSubsystem.v1_0_0.json
Test:
1. Validator passed.
2. doGet method:
~$ curl -k -H "X-Auth-Token: $token" -X GET https://${bmc}/redfish/v1/Chassis/chassis/ThermalSubsystem
{
"@odata.id": "/redfish/v1/Chassis/chassis/ThermalSubsystem",
"@odata.type": "#ThermalSubsystem.v1_0_0.ThermalSubsystem",
"Id": "chassis",
"Name": "Thermal Subsystem for Chassis",
"Status": {
"Health": "OK",
"State": "Enabled"
}
}
3. A bad chassis ID:
~$ curl -k -H "X-Auth-Token: $token" -X GET https://${bmc}/redfish/v1/Chassis/chassisSSBAD/ThermalSubsystem
{
"error": {
"@Message.ExtendedInfo": [
{
"@odata.type": "#Message.v1_1_1.Message",
"Message": "The requested resource of type Chassis named chassisSSBAD was not found.",
"MessageArgs": [
"Chassis",
"chassisSSBAD"
],
"MessageId": "Base.1.8.1.ResourceNotFound",
"MessageSeverity": "Critical",
"Resolution": "Provide a valid resource identifier and resubmit the request."
}
],
"code": "Base.1.8.1.ResourceNotFound",
"message": "The requested resource of type Chassis named chassisSSBAD was not found."
}
}
Signed-off-by: Xiaochao Ma <maxiaochao@inspur.com>
Change-Id: Ib19879f584304e5303f1a83d88bdd18c78a61633
Signed-off-by: Zhenwei Chen <zhenweichen0207@gmail.com>
Diffstat (limited to 'Redfish.md')
-rw-r--r-- | Redfish.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/Redfish.md b/Redfish.md index e964c2cc41..0270208a6a 100644 --- a/Redfish.md +++ b/Redfish.md @@ -223,6 +223,11 @@ Chassis to Drives, The name of the association is "chassis<->drive") - MinNumNeeded - MaxNumSupported +#### /redfish/v1/Chassis/{ChassisId}/ThermalSubsystem + +##### ThermalSubsystem +- Status + #### /redfish/v1/Chassis/{ChassisId}/Power/ ##### Power PowerControl Voltages PowerSupplies Redundancy |