Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / bmcweb / 9edd866c3ad31dfff3b3ad4a14c5fa2c4669c00e
commit9edd866c3ad31dfff3b3ad4a14c5fa2c4669c00e[log] [tgz]
authorChalapathi Venkataramashetty <chalapathix.venkataramashetty@intel.com>Mon May 25 20:14:52 2020 +0000
committerAppaRao Puli <apparao.puli@linux.intel.com>Mon Aug 03 19:36:49 2020 +0000
tree9202e0ca3780a11ead210cfa4343a3a51a15b3d9
parenteb7d3d5400555715d755ed03722dbbfe2b6607c9 [diff]
Add message registry entry for successful fw update staging

Add an event log in redfish when fw completed writing to staging area
during firmware update.

Tested:
Update BMC firmware
POST: https://<BMC_IP>/redfish/v1/UpdateService/
      with <BMC_Update_Capsule> binary file
After BMC reboots with successful update check for Event log in
Redfish
Command: GET: https://<BMC_IP>/redfish/v1/Systems/system/LogServices/
              EventLog/Entries
Response:
{
      "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/
                    Entries/1595803968",
      "@odata.type": "#LogEntry.v1_4_0.LogEntry",
      "Created": "2020-07-26T22:52:48+00:00",
      "EntryType": "Event",
      "Id": "1595803968",
      "Message": "BMC firmware update to version 00.74 staged
                  successfully.",
      "MessageArgs": [
        "BMC",
        "00.74"
      ],
      "MessageId": "OpenBMC.0.1.FirmwareUpdateStaged",
      "Name": "System Event Log Entry",
      "Severity": "OK"
    },

Signed-off-by: Chalapathi Venkataramashetty <chalapathix.venkataramashetty@intel.com>
Change-Id: I62aad007c7fc8d311a351d1c5ec4e84d6b4a77ad
1 file changed
tree: 9202e0ca3780a11ead210cfa4343a3a51a15b3d9
  1. cmake/
  2. http/
  3. include/
  4. redfish-core/
  5. scripts/
  6. src/
  7. static/
  8. .clang-format
  9. .dockerignore
  10. .gitignore
  11. bmcweb.service.in
  12. bmcweb.socket
  13. build_x86.sh
  14. build_x86_docker.sh
  15. cmake-format.json
  16. CMakeLists.txt
  17. CMakeLists.txt.in
  18. config.h.in
  19. DEVELOPING.md
  20. Dockerfile
  21. Dockerfile.base
  22. JenkinsFile
  23. LICENCE
  24. MAINTAINERS
  25. pam-webserver
  26. README.md
  27. 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.