Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / bmcweb / bc6be2376b4a5407e51deab72b1a4c8a1b7fd425
commitbc6be2376b4a5407e51deab72b1a4c8a1b7fd425[log] [tgz]
authorjayaprakash Mutyala <mutyalax.jayaprakash@intel.com>Tue Dec 24 19:15:58 2019 +0000
committerJayaprakash Mutyala <mutyalax.jayaprakash@intel.com>Fri Jan 17 17:45:52 2020 +0000
tree21be97d802520ac0df15f40a02211686c10500fe
parent2b5e08e2915d886655a78aaabff40745dca6b517 [diff]
msg_registry: updated MemoryThermTrip msg entry

Updated "MemoryThermTrip" message entry for CPU Memory
Thermal Trip events.

Tested:
1. Redfish validator - passed for this new addition
2. Verified in Redfish, MemoryThermTrip message populated properly

Redfish URI:
GET: https://<BMC IP>/redfish/v1/Systems/system/LogServices/EventLog
               /Entries
{
      "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
      "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/
                    Entries/506",
      "@odata.type": "#LogEntry.v1_4_0.LogEntry",
      "Created": "1970-01-01T00:08:26+00:00",
      "EntryType": "Event",
      "Id": "506",
      "Message": "Memory ThermTrip asserted: CPU 1.",
      "MessageArgs": [
        "CPU 1"
      ],
      "MessageId": "OpenBMC.0.1.MemoryThermTrip",
      "Name": "System Event Log Entry",
      "Severity": "Critical"
}
{
      "@odata.context": "/redfish/v1/$metadata#LogEntry.LogEntry",
      "@odata.id": "/redfish/v1/Systems/system/LogServices/EventLog/
                    Entries/506_2",
      "@odata.type": "#LogEntry.v1_4_0.LogEntry",
      "Created": "1970-01-01T00:08:26+00:00",
      "EntryType": "Event",
      "Id": "506_2",
      "Message": "Memory ThermTrip asserted: CPU 2.",
      "MessageArgs": [
        "CPU 2"
      ],
      "MessageId": "OpenBMC.0.1.MemoryThermTrip",
      "Name": "System Event Log Entry",
      "Severity": "Critical"
}

Signed-off-by: jayaprakash Mutyala <mutyalax.jayaprakash@intel.com>
Signed-off-by: Chalapathi <chalapathix.venkataramashetty@intel.com>
Change-Id: I89271d28012c7f01a6cc37e1ef35c7e15f5e9965
1 file changed
tree: 21be97d802520ac0df15f40a02211686c10500fe
  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.