BMC/OpenBmc/bmcweb.git/redfish-core/schema/oem, branch master

OpenBMCManager: fix v1_1_0.Manager BaseType

2026-06-25T18:33:29+00:00

The OpenBMCManager.v1_1_0.Manager ComplexType was inheriting from Resource.OemObject instead of OpenBMCManager.v1_0_0.Manager, silently dropping all v1_0_0 properties including the Certificates NavigationProperty from the schema. This was causing the bmcweb bumps to fail. As explained to me, because openbmc_managers.hpp emits "@odata.type": "#OpenBMCManager.v1_1_0.Manager" at runtime, the Redfish Service Validator resolves every Oem/OpenBmc property against that type. With Certificates absent from the type definition, the RSV raised an Unknown Property Error on Oem/OpenBmc/Certificates. Fix the BaseType to OpenBMCManager.v1_0_0.Manager so v1_1_0 inherits Certificates and any other v1_0_0. This is the standard CSDL versioning pattern. This was introduced by 762a74183 [1]. [1]: https://gerrit.openbmc.org/c/openbmc/bmcweb/+/85785. Tested: Inspection only. Change-Id: I95b8a27f1b3b86192c34f61fb3a48d2d42a4df6d Signed-off-by: Gunnar Mills

bmcweb: expose PID D term and hysteresis mode in OEM schema

2026-06-22T17:39:02+00:00

Extend the OpenBMCManager OEM fan configuration to cover the two additional PID parameters already supported by phosphor-pid-control: * DCoefficient (derivative term of the PID loop) * CheckHysteresisWithSetpoint (boolean indicating whether input hysteresis is applied around the setpoint) These fields are now exposed through the Oem/OpenBmc/Fan/PidControllers Redfish interface and correctly mapped to the underlying D-Bus PidConfiguration objects. To keep the OEM schema backwards compatible, introduce a new version OpenBMCManager.v1_1_0 that adds the two properties to the PidController definition, and update bmcweb to reference the new schema version. Test(qemu evb-ast2600): Load Fantable via entity-manager /var/configuration/system.json content: https://github.com/YouPengWu/ToReviewer/blob/main/85785 /Test_case/Bmcweb(my_commit)/system.txt Verify OEM properties in Manager resource GET /redfish/v1/Managers/bmc: https://github.com/YouPengWu/ToReviewer/blob/main/85785 /Test_case/Bmcweb(my_commit)/Managers-bmc-oem.png Verify OpenBMCManager OEM schema exposure GET /redfish/v1/JsonSchemas/OpenBMCManager: https://github.com/YouPengWu/ToReviewer/blob/main/85785 /Test_case/Bmcweb(my_commit)/redfish-oem-schema.png Run Redfish Service Validator (RSV) Summary: https://github.com/YouPengWu/ToReviewer/blob/main/85785 /Test_case/Bmcweb(my_commit)/redfish-validator-summary.png Details: https://github.com/YouPengWu/ToReviewer/blob/main/85785 /Test_case/Bmcweb(my_commit)/redfish-validator-details.png Full log: https://github.com/YouPengWu/ToReviewer/blob/main/85785 /Test_case/Bmcweb(my_commit)/ConformanceLog_12_14_2025_180449.txt Baseline (community/original) RSV log for comparison (no new failures introduced): https://github.com/YouPengWu/ToReviewer/blob/main/85785 /Test_case/Bmcweb(57d41)/ConformanceLog_12_14_2025_174610.txt Change-Id: Ide1a118f9fd27eb94e911997d99e5934fe3e1095 Signed-off-by: You Peng Wu

Fix Oem/OpenBMC Redfish Service Validator warnings

2026-02-27T18:06:55+00:00

There are a few warnings like - Schema error to missing OpenBMCManager schema on BMC ``` Oem/OpenBmc Schema Error: Unable to locate the schema definition for the 'OpenBMCManager.v1_0_0.Manager' type. ``` ``` curl -k -X GET https://${bmc}/redfish/v1/Managers/bmc "Oem": { "OpenBmc": { "@odata.id": "/redfish/v1/Managers/bmc#/Oem/OpenBmc", "@odata.type": "#OpenBMCManager.v1_0_0.Manager", "Certificates": { "@odata.id": "/redfish/v1/Managers/bmc/Truststore/Certificates" } } ``` - Schema error to missing OpenBMCAccountService schema on BMC ``` Oem/OpenBMC [Object] Schema Error: Unable to locate the schema definition for the 'OpenBMCAccountService.v1_0_0.AccountService' type. ``` ``` curl -k -X GET https://${bmc}/redfish/v1/AccountService ... "Oem": { "OpenBMC": { "@odata.id": "/redfish/v1/AccountService#/Oem/OpenBMC", "@odata.type": "#OpenBMCAccountService.v1_0_0.AccountService", "AuthMethods": { "BasicAuth": true, "Cookie": true, "SessionToken": true, "TLS": false, "XToken": true } } }, ``` - Unexpected trailing slash ``` @odata.id /redfish/v1/Managers/bmc/Truststore/Certificates/ Trailing Slash Warning: The URI for the resource has an unexpected trailing slash. ``` ``` curl -k -X GET https://${bmc}/redfish/v1/Managers/bmc/Truststore/Certificates { "@odata.id": "/redfish/v1/Managers/bmc/Truststore/Certificates/", "@odata.type": "#CertificateCollection.CertificateCollection", "Description": "A Collection of TrustStore certificate instances", "Members": [], "Members@odata.count": 0, "Name": "TrustStore Certificates Collection” ``` Tested: - Redfish Service Validator passes on the above cases without warnings Change-Id: Ib2d2d765101e9d7820531f307164cef96a7705cf Signed-off-by: Myung Bae

Remove unused OemComputerSystem json file

2024-09-09T15:18:14+00:00

The previous commit 1d834d4[1] renamed OemComputerSystem json to OpenBmcComputerSystem json, but forgot to delete the old one. Tested: Inspection only. [1] https://github.com/openbmc/bmcweb/commit/1d834d49cc0d2dcee11f203b167434aeefcb7970 Change-Id: Ia5512f0c9ea249742e0ac5fa3c7d0d120f824c36 Signed-off-by: Myung Bae

Fix OpenBMC JsonSchemas installation

2024-09-07T15:27:46+00:00

This fixes the missing Oem/OpenBMC JsonSchema file installation. Tested: - Check JsonSchemas to have the enabled OpenBMC schemas ``` curl -k -X GET https::/${bmc}/redfish/v1/JsonSchemas/OpenBMCAccountService curl -k -X GET https::/${bmc}/redfish/v1/JsonSchemas/OpenBMCManager curl -k -X GET https::/${bmc}/redfish/v1/JsonSchemas/OpenBMCComputerSystem ``` Change-Id: Ia13b5c5d1626ee5648ddce5cd62375c8e3e09e75 Signed-off-by: Myung Bae

Format OEM schemas with xmllint

2024-09-05T15:40:56+00:00

Our OEM schemas still have whitespace violations. Reformat using xmllint --format. Tested: Whitespace changes only. Code compiles. Change-Id: Ic240d7b7c617991005d72313183b20d452273662 Signed-off-by: Ed Tanous

Correct OpenBMCComputerSystem schema content

2024-09-05T15:40:34+00:00

Correct the incorrect collection uri of OpenBMCComputerSystem_v1.xml. Tested: - Verify that the old uri is invalid - Verify that the corrected uri is valid Change-Id: Ica013733d995da0e41711eca715609b54b161e1d Signed-off-by: Myung Bae

Reformat meson files with meson format

2024-08-26T20:37:01+00:00

Meson recently got a new format command in 1.5.0 [1]. It makes slightly different formatting decisions compared to muon (what we used previously) but given it's the official tool, we should switch to it. There is one bug resolved recently that requires this format be done using the meson from master. Ideally this would be enforced by CI in the future, but that's WIP. Tested: Whitespace only, code compiles. [1] https://mesonbuild.com/Commands.html#format [2] https://github.com/mesonbuild/meson/commit/df706807239095ddbbfd2975b3fe067ad6b5d535 Change-Id: I91506efb659c431e913c717d8a26aa349fccbd75 Signed-off-by: Ed Tanous

Remove old symlinks

2024-07-29T22:34:26+00:00

These symlinks no longer point to anything useful. Tested: Code compiles. GET /redfish/v1/\$metadata returns correct data. Change-Id: I29853e18f85d9509e171b0460792ac788fd503ec Signed-off-by: Ed Tanous

Update copyright and schema location

2024-07-23T21:01:32+00:00

It's now 2024, and the schemas have moved. Update the canonical location in the code. Change-Id: Iaed97f347a17e2685845081828be0a3a2f72a38a Signed-off-by: Ed Tanous