Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / bmcweb / 156d6b00a9dc06ac9f618ecd8d5fc6b1b49d5be4
commit156d6b00a9dc06ac9f618ecd8d5fc6b1b49d5be4[log] [tgz]
authorAppaRao Puli <apparao.puli@linux.intel.com>Sat Apr 25 06:04:05 2020 +0530
committerAppaRao Puli <apparao.puli@linux.intel.com>Thu May 14 01:09:21 2020 +0000
tree874fd69b33be5f9da033b10b01b340b74595b1e2
parente46946ac9e5c72dbd63d36e420dba417243346bb [diff]
EventService: Add MetricReport support

Add Telemetry metric report support to EventService.
 - Adding MetricReport support to schema implemenation.
 - Dynamically register and unregister the metric report
   signal.
 - Reads Telemtry data using D-Bus calls.
 - Filter the metric reports depending on user configured
   MetricReportDefinition.
 - Format the Telemetry readings as per MetricReport schema.
 - Send the formatted data to the client.

Tested:
 - HTTP client successfully received asynchronous metric
   reports data.
 - valdiated the register and unregister by adding and
   deleting subscriptions.
 - Ran Redfish validator successfully.

Change-Id: I7b59ac3ecad169a7959a800730dbc2fe85baf068
Signed-off-by: AppaRao Puli <apparao.puli@linux.intel.com>
2 files changed
tree: 874fd69b33be5f9da033b10b01b340b74595b1e2
  1. cmake/
  2. http/
  3. include/
  4. redfish-core/
  5. scripts/
  6. src/
  7. static/
  8. .clang-format
  9. .gitignore
  10. bmcweb.service.in
  11. bmcweb.socket
  12. build_x86.sh
  13. cmake-format.json
  14. CMakeLists.txt
  15. CMakeLists.txt.in
  16. config.h.in
  17. DEVELOPING.md
  18. JenkinsFile
  19. LICENCE
  20. MAINTAINERS
  21. pam-webserver
  22. README.md
  23. Redfish.md
README.md

OpenBMC webserver

This component attempts to be a "do everything" embedded webserver for openbmc.

Capabilities

At this time, the webserver implements a few interfaces:

  • Authentication middleware that supports cookie and token based authentication, as well as CSRF prevention backed by linux PAM authentication credentials.
  • An (incomplete) attempt at replicating phosphor-dbus-rest interfaces in C++. Right now, a few of the endpoint definitions work as expected, but there is still a lot of work to be done. The portions of the interface that are functional are designed to work correctly for phosphor-webui, but may not yet be complete.
  • Replication of the rest-dbus backend interfaces to allow bmc debug to logged in users.
  • An initial attempt at a read-only redfish interface. Currently the redfish interface targets ServiceRoot, SessionService, AccountService, Roles, and ManagersService. Some functionality here has been shimmed to make development possible. For example, there exists only a single user role.
  • SSL key generation at runtime. See the configuration section for details.
  • Static file hosting. Currently, static files are hosted from the fixed location at /usr/share/www. This is intended to allow loose coupling with yocto projects, and allow overriding static files at build time.
  • Dbus-monitor over websocket. A generic endpoint that allows UIs to open a websocket and register for notification of events to avoid polling in single page applications. (this interface may be modified in the future due to security concerns.

Configuration

BMCWeb is configured by setting -D flags that correspond to options in bmcweb/CMakeLists.txt and then compiling. For example, cmake -DBMCWEB_ENABLE_KVM=NO ... followed by make. The option names become C++ preprocessor symbols that control which code is compiled into the program.

When BMCWeb starts running, it reads persistent configuration data (such as UUID and session data) from a local file. If this is not usable, it generates a new configuration.

When BMCWeb SSL support is enabled and a usable certificate is not found, it will generate a self-sign a certificate before launching the server. The keys are generated by the secp384r1 algorithm. The certificate

  • is issued by C=US, O=OpenBMC, CN=testhost,
  • is valid for 10 years,
  • has a random serial number, and
  • is signed using the SHA-256 algorithm.