Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / bmcweb / d82a3acd1abc04a13f90cef5234416c3e18da0e1
commitd82a3acd1abc04a13f90cef5234416c3e18da0e1[log] [tgz]
authorCarol Wang <wangkair@cn.ibm.com>Thu Nov 21 13:56:38 2019 +0800
committerCarol Wang <wangkair@cn.ibm.com>Thu Dec 05 11:24:04 2019 +0800
treef8c3dfaaa16bc5a812c7a15ab1376bd18a2403ba
parent274dfe625f862e8ded2d4eb88dd856cf66bf54bf [diff]
Redfish: Implement ResetBios action

This action resets the BIOS attributes to default.

Tested:
GET test:
1. $ curl -k -H "X-Auth-Token: $token" https://${bmc}/redfish/v1/Systems/system
{
  ...
  "Bios": {
    "@odata.id": "/redfish/v1/Systems/system/Bios"
  },
  ...
}
2. $ curl -k -H "X-Auth-Token: $token" https://${bmc}/redfish/v1/Systems/system/Bios
{
  "@odata.id": "/redfish/v1/Systems/system/Bios",
  "@odata.type": "#Bios.v1_1_0.Bios",
  "Actions": {
    "#Bios.ResetBios": {
      "target": "/redfish/v1/Systems/system/Bios/Actions/Bios.ResetBios"
    }
  },
  "Description": "BIOS Configuration Service",
  "Id": "BIOS",
  "Name": "BIOS Configuration"
}

POST test:
1. Change gard list:
 # ./gard list
 No GARD entries to display
 # ./gard create /Sys0/Node0/Proc1/EQ1/EX1/Core0
 # ./gard list
  ID       | Error    | Type       | Path
 -----------------------------------------------------------------------
  00000001 | 00000000 | Manual     | /Sys0/Node0/Proc1/EQ1/EX1/Core0
 =======================================================================
2. Reset bios:
 # curl -k -H "X-Auth-Token: $token" -X POST https://${bmc}/redfish/v1/Systems/system/Bios/Actions/Bios.ResetBios
3. Check gard list again:
 # ./gard list
 No GARD entries to display

Validator tool test:
 Counter({'pass': 3001, 'skipOptional': 2475, 'metadataNamespaces': 1605,
 'passGet': 191, 'serviceNamespaces': 72, 'invalidPropertyValue': 10,
 'passAction': 7, 'optionalAction': 6, 'warningPresent': 6, 'warnDeprecated':
 2, 'unverifiedComplexAdditional': 1})
 Validation has succeeded.

Signed-off-by: Carol Wang <wangkair@cn.ibm.com>
Change-Id: I0cba966bfde04566001b6df07ad15217f627c327
3 files changed
tree: f8c3dfaaa16bc5a812c7a15ab1376bd18a2403ba
  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. DEVELOPING.md
  17. JenkinsFile
  18. LICENCE
  19. MAINTAINERS
  20. pam-webserver
  21. README.md
  22. 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.