Google Git
Sign in
gbmc / gbmcweb / e89c7644c689d68f2d0d96b21695aa45eaf6c653
commite89c7644c689d68f2d0d96b21695aa45eaf6c653[log] [tgz]
authorEdward Lee <edwarddl@google.com>Tue Sep 19 21:36:45 2023 +0000
committerEdward Lee <edwarddl@google.com>Wed Sep 20 19:27:12 2023 +0000
treebe77c2485a30cad99d96ab582e9a16b4cc024579
parent1c296bbee62b416e1d100c43dbdec44a552511d8 [diff]
Fix Multi-Host CPU and DIMM Logic

The old logic was testing on CPU and DIMM objects that had a path
hierarchy of being a direct child of system's DBus objects. When
this assumption was not valid anymore, we have to check to see
whether DIMM's object exists as any descendent of the system's DBus
object.

This affected both querying DIMMs and CPU Efficient Expand

Tested:
Queried all of the following and have valid responses
/redfish/v1/Systems/<systemId>/Memory/<dimmId>
/redfish/v1/Systems/<systemId>/Memory/<dimmId>?\$expand=.
/redfish/v1/Systems/<systemId>/Processor/<cpuId>?\$expand=.

Google-Bug-Id: 301121308
Change-Id: Ic716c2b65bb4aefb0dac43785563b42141cb59c3
Signed-off-by: Edward Lee <edwarddl@google.com>
2 files changed
tree: be77c2485a30cad99d96ab582e9a16b4cc024579
  1. .github/
  2. config/
  3. grpc-redfish/
  4. http/
  5. include/
  6. mapper/
  7. plugins/
  8. redfish-core/
  9. scripts/
  10. src/
  11. static/
  12. subprojects/
  13. test/
  14. .clang-format
  15. .clang-tidy
  16. .dockerignore
  17. .gitignore
  18. .markdownlint.yaml
  19. .openbmc-enforce-gitlint
  20. .prettierignore
  21. .shellcheck
  22. AGGREGATION.md
  23. CLIENTS.md
  24. COMMON_ERRORS.md
  25. DBUS_USAGE.md
  26. DEVELOPING.md
  27. HEADERS.md
  28. LICENSE
  29. meson.build
  30. meson_options.txt
  31. OEM_SCHEMAS.md
  32. OWNERS
  33. README.md
  34. Redfish.md
  35. run-ci
  36. setup.cfg
  37. TESTING.md
README.md

OpenBMC webserver

==============================================================================

This component attempts to be a “do everything” embedded webserver for OpenBMC.

Features

The webserver implements a few distinct interfaces:

  • DBus event websocket. Allows registering on changes to specific dbus paths, properties, and will send an event from the websocket if those filters match.
  • OpenBMC DBus REST api. Allows direct, low interference, high fidelity access to dbus and the objects it represents.
  • Serial: A serial websocket for interacting with the host serial console through websockets.
  • Redfish: A protocol compliant, DBus to Redfish translator.
  • KVM: A websocket based implementation of the RFB (VNC) frame buffer protocol intended to mate to webui-vue to provide a complete KVM implementation.

Protocols

bmcweb at a protocol level supports http and https. TLS is supported through OpenSSL.

AuthX

Authentication

Bmcweb supports multiple authentication protocols:

  • Basic authentication per RFC7617
  • Cookie based authentication for authenticating against webui-vue
  • Mutual TLS authentication based on OpenSSL
  • Session authentication through webui-vue
  • XToken based authentication conformant to Redfish DSP0266

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.

Authorization

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.

Configuration

bmcweb is configured per the meson build files. Available options are documented in meson_options.txt

Compile bmcweb with default options

meson 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.

Use of persistent data

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.

TLS certificate generation

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.

Redfish Aggregation

bmcweb is capable of aggregating resources from satellite BMCs. Refer to AGGREGATION.md for more information on how to enable and use this feature.