commit | a56174963e1d8bd9fc90cdeb3aa7f1b7f2e0dca4 | [log] [tgz] |
---|---|---|
author | Jie Yang <jjy@google.com> | Tue Jun 29 12:59:14 2021 -0700 |
committer | Ed Tanous <ed@tanous.net> | Fri Jun 30 21:06:10 2023 +0000 |
tree | ae7b21abc66cad23f0d88ef539a4a63b5770764e | |
parent | 1d7c0f08e5c3f61f2b32b99f5c9579661d757194 [diff] |
Add topology links for Chassis Implement the physical topology design[0] for Chassis resources to report which Chassis contain or are contained by other Chassis. Query this information from the object mapper using associations defined in phosphor-dbus-interfaces[1] and make it available in the Links section of the Redfish result. [0] https://gerrit.openbmc.org/c/openbmc/docs/+/54205 [1] https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/58441 Tested: Built for evb-ast2600 with example JSON configs and ran in QEMU Ran Redfish Service Validator with no new warnings Sample output: ''' curl -k -u root:0penBmc -X GET https://127.0.0.1:60443/redfish/v1/Chassis/Subchassis { "@odata.id": "/redfish/v1/Chassis/Subchassis", "@odata.type": "#Chassis.v1_16_0.Chassis", ... "Id": "Subchassis", "Links": { "ComputerSystems": [ { "@odata.id": "/redfish/v1/Systems/system" } ], "ContainedBy": { "@odata.id": "/redfish/v1/Chassis/Superchassis" }, "ManagedBy": [ { "@odata.id": "/redfish/v1/Managers/bmc" } ] }, ... } curl -k -u root:0penBmc -X GET https://127.0.0.1:60443/redfish/v1/Chassis/Superchassis { "@odata.id": "/redfish/v1/Chassis/Superchassis", "@odata.type": "#Chassis.v1_16_0.Chassis", ... "Id": "Superchassis", "Links": { "ComputerSystems": [ { "@odata.id": "/redfish/v1/Systems/system" } ], "Contains": [ { "@odata.id": "/redfish/v1/Chassis/Subchassis" } ], "Contains@odata.count": 1, "ManagedBy": [ { "@odata.id": "/redfish/v1/Managers/bmc" } ] }, ... } ''' Signed-off-by: Jie Yang <jjy@google.com> Signed-off-by: Zhenwei Chen <zhenweichen0207@gmail.com> Signed-off-by: Benjamin Fair <benjaminfair@google.com> Change-Id: Idc4c3e99b8269bcc5f94112e977a89970abd0bf3
This component attempts to be a "do everything" embedded webserver for OpenBMC.
The webserver implements a few distinct interfaces:
bmcweb at a protocol level supports http and https. TLS is supported through OpenSSL.
Bmcweb supports multiple authentication protocols:
Each of these types of authentication is able to be enabled or disabled both via runtime policy changes (through the relevant Redfish APIs) or via configure time options. All authentication mechanisms supporting username/password are routed to libpam, to allow for customization in authentication implementations.
All authorization in bmcweb is determined at routing time, and per route, and conform to the Redfish PrivilegeRegistry.
*Note: Non-Redfish functions are mapped to the closest equivalent Redfish privilege level.
bmcweb is configured per the meson build files. Available options are documented in meson_options.txt
meson setup builddir ninja -C builddir
If any of the dependencies are not found on the host system during configuration, meson will automatically download them via its wrap dependencies mentioned in bmcweb/subprojects
.
bmcweb relies on some on-system data for storage of persistent data that is internal to the process. Details on the exact data stored and when it is read/written can seen from the persistent_data
namespace.
When SSL support is enabled and a usable certificate is not found, bmcweb will generate a self-signed a certificate before launching the server. Please see the bmcweb source code for details on the parameters this certificate is built with.
bmcweb is capable of aggregating resources from satellite BMCs. Refer to AGGREGATION.md for more information on how to enable and use this feature.