Google Git
Sign in
gbmc / gbmcweb / refs/heads/master
commitbacae89f73711326d05f81a09effe0f37c4073c8[log] [tgz]
authorgBMC Team <gbmc-core@google.com>Mon Sep 15 11:40:34 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Mon Sep 15 11:41:17 2025 -0700
tree2e78ebd88d387f539c2db6dde5d76f45568604e3
parent996db7ecda8e166c8dd8ccac3746b97fd4682e45 [diff]
tlbmc: integrate metric_collector as a running portion of tlBMC

This change adds the `metric_collector` as a running part of tlBMC if configured to do so via textproto configs.

Adds metric_collector to the tlBMC storage, in order to actually start collecting software metrics

Integrate proto config parser to parse metric_collector configs

Added `metrics` route to fetch and serve software_metrics as defined by the resource.

Meson for Yocto builds updated

Copybara updated to include all new files related to software metrics collection that are needed to build properly.

tlbmc configs updated to reflect metric_collector addition

test JSON files updated

PiperOrigin-RevId: 807320873
Change-Id: Ic7e8e12a16d09c077390aae95a850e9b4c2b51c5
22 files changed
tree: 2e78ebd88d387f539c2db6dde5d76f45568604e3
  1. .github/
  2. config/
  3. g3/
  4. http/
  5. include/
  6. install/
  7. plugins/
  8. redfish-core/
  9. redfish_authorization/
  10. scripts/
  11. src/
  12. static/
  13. subprojects/
  14. test/
  15. tlbmc/
  16. .clang-format
  17. .clang-tidy
  18. .clang-tidy-ignore
  19. .dockerignore
  20. .gitignore
  21. .markdownlint.yaml
  22. .openbmc-enforce-gitlint
  23. .openbmc-no-clang
  24. .prettierignore
  25. .shellcheck
  26. AGGREGATION.md
  27. CLIENTS.md
  28. COMMON_ERRORS.md
  29. copy.bara.sky
  30. DBUS_USAGE.md
  31. DEVELOPING.md
  32. gcovr.cfg
  33. HEADERS.md
  34. LICENSE
  35. meson.build
  36. meson_options.txt
  37. OEM_SCHEMAS.md
  38. OWNERS
  39. PLUGINS.md
  40. README.md
  41. README_GOOGLE.md
  42. Redfish.md
  43. run-ci
  44. setup.cfg
  45. TESTING.md
  46. 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.