Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / bmcweb / 42cbe53889b5f2d358d1174245df51a23efcb3f8
commit42cbe53889b5f2d358d1174245df51a23efcb3f8[log] [tgz]
authorGunnar Mills <gmills@us.ibm.com>Thu Aug 15 15:26:54 2019 -0500
committerGunnar Mills <gmills@us.ibm.com>Fri Feb 07 21:15:21 2020 +0000
tree8de0ec405599a92e7cfbc8fb4d55669d96ae36c9
parent2077899f6d4534d98ca2cca3bc9020dbc6a4aef9 [diff]
Add Power Supply Attributes

Map DeratingFactor from PowerSupplyAttributes.interface.yaml
to the Redfish property PowerSupply "EfficiencyPercent".

Only do this call when the "Power" schema is called.
Use the InventoryItem class introduced in
adc4f0db57568c5e5d2a3398fce00dbb050a3b72

Tested: Power, Thermal, all look good.
        Passed the Redfish Validator.
  "PowerSupplies": [
    {
      "@odata.id": "/redfish/v1/Chassis/chassis/Power#/PowerSupplies/0",
      "EfficiencyPercent": 90,
      "IndicatorLED": "Off",
      "Manufacturer": "",
      "MemberId": "powersupply0",
      "Model": "2B1D",
      "Name": "powersupply0",
      "PartNumber": "01KL471",
      "PowerInputWatts": 12.0,
      "SerialNumber": "71G370",
      "Status": {
        "Health": "OK",
        "State": "Enabled"
      }
    },

Change-Id: I344577a7a3d72cd37d5f6bab03edbdce13b9f764
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
1 file changed
tree: 8de0ec405599a92e7cfbc8fb4d55669d96ae36c9
  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 prime256v1 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.