Google Git
Sign in
gbmc / gbmcweb / 9168ddc77baacab822710ff4e3c7ab2cd49e0f9f
commit9168ddc77baacab822710ff4e3c7ab2cd49e0f9f[log] [tgz]
authorDavid Tang <davtang@google.com>Wed May 21 17:44:35 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Wed May 21 17:45:15 2025 -0700
tree00613e0512c13b261a116f5e802b26889e42b0fe
parent677598a7711f7cd2b568aa6941f65f6a4034e807 [diff]
Propagate Assembly sensors to parent board

Implement logic to propagate all sensors configured in the EM config of an Assembly to the parent board. This involves:

1. Creation of a Assembly to Parent Config Board map to perform lookup at sensor creation time to correctly assign ownership of the Assembly sensors to the parent config board. This map is populated at topology creation time. If a sensor's assigned board_config_name is in this map, it indicates that this is an Assembly, and therefore we must override the set board_config_name.

    Note: Since Assemblies are a concept specific to Redfish, this is implemented in the RedfishIndexes field of the EntityConfig. As future protocols are supported, similar fields may be added to support concepts specific to different protocols.

2. Logic for sensor board_config_name override at sensor creation time. Since sensor configs are immutable outside of entity_config_json_impl.cc, we need to provide an override field when sensors are created to propagate sensors correctly to parent board and avoid the board_config_name set when the sensor was originally parsed.

3. Default RelatedItem assigning for Assemblies. Since we have now propagated the parent Board to the created Sensor's EntityCommonConfig, if the RelatedItem for a sensor is still an Assembly type, indicating that the RelatedItem was not overridden in EM config, we assign the parent board as the RelatedItem.

#tlbmc

Tested: unit tests and e2e test in follow up cl/759162080
PiperOrigin-RevId: 761737715
Change-Id: I65ba2638aeeb0f376f4a7ac03ad5f054e30464a7
3 files changed
tree: 00613e0512c13b261a116f5e802b26889e42b0fe
  1. .github/
  2. config/
  3. g3/
  4. http/
  5. include/
  6. plugins/
  7. redfish-core/
  8. redfish_authorization/
  9. scripts/
  10. src/
  11. static/
  12. subprojects/
  13. test/
  14. tlbmc/
  15. .clang-format
  16. .clang-tidy
  17. .clang-tidy-ignore
  18. .dockerignore
  19. .gitignore
  20. .markdownlint.yaml
  21. .openbmc-enforce-gitlint
  22. .openbmc-no-clang
  23. .prettierignore
  24. .shellcheck
  25. AGGREGATION.md
  26. CLIENTS.md
  27. COMMON_ERRORS.md
  28. DBUS_USAGE.md
  29. DEVELOPING.md
  30. gcovr.cfg
  31. HEADERS.md
  32. LICENSE
  33. meson.build
  34. meson_options.txt
  35. OEM_SCHEMAS.md
  36. OWNERS
  37. PLUGINS.md
  38. README.md
  39. README_GOOGLE.md
  40. Redfish.md
  41. run-ci
  42. setup.cfg
  43. TESTING.md
  44. UNIT_TESTING.md
README.md

OpenBMC webserver

This project is Google's version of BMCWeb.

See Readme Google for Google added features. The following is the original README of OpenBMC/BMCWeb.

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

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.