add design: firmware_update_via_blobs

Firmware update process using the Blob protocol over IPMI.  This process
will allow legacy and UBI image uploads over IPMI/P2A/LPC with signature
verification.  Each platform can provide modifications to the handler
behavior or add custom handlers as needed.  The firmware update process
will be just another blob handler and therefore implement the
appropriate blob protocol primitives.

Change-Id: I7e18a7900c878d5d9205a8c1b8475e71a1bceeb3
Signed-off-by: Patrick Venture <venture@google.com>
1 file changed
tree: e35a15c344eb2d2835e49506bc86d06f151f911c
  1. code-update/
  2. designs/
  3. development/
  4. logo/
  5. meetings/
  6. security/
  7. style/
  8. userguide/
  9. cheatsheet.md
  10. console.md
  11. CONTRIBUTING.md
  12. cpp-style-and-conventions.md
  13. host-management.md
  14. ipmi-architecture.md
  15. kernel-development.md
  16. LED-architecture.md
  17. LICENSE
  18. maintainer-workflow.md
  19. MAINTAINERS
  20. Makefile
  21. object-mapper.md
  22. openbmc-conversion.md
  23. openbmc-systemd.md
  24. README.md
  25. REDFISH-cheatsheet.md
  26. rest-api.md
  27. REST-cheatsheet.md
  28. run-test-docker.md
  29. sensor-architecture.md
  30. subtree.md
  31. user_management.md
  32. yocto-development.md
README.md

OpenBMC documentation

This repository contains documentation for OpenBMC as a whole. There may be component-specific documentation in the repository for each component.

OpenBMC Usage

These documents describe how to use OpenBMC, including using the programmatic interfaces to an OpenBMC system.

OpenBMC Development

These documents contain details on developing OpenBMC code itself

OpenBMC Goals

The OpenBMC project's aim is to create a highly extensible framework for BMC software and implement for data-center computer systems.

We have a few high-level objectives:

  • The OpenBMC framework must be extensible, easy to learn, and usable in a variety of programming languages.

  • Provide a REST API for external management, and allow for "pluggable" interfaces for other types of management interactions.

  • Provide a remote host console, accessible over the network

  • Persist network configuration settable from REST interface and host

  • Provide a robust solution for RTC management, exposed to the host.

  • Compatible with host firmware implementations for basic IPMI communication between host and BMC

  • Provide a flexible and hierarchical inventory tracking component

  • Maintain a sensor database and track thresholds

Technical Steering Committee

  • Brad Bishop (chair), IBM
  • Nancy Yuen, Google
  • Sai Dasari, Facebook
  • James Mihm, Intel
  • Ali Larijani, Microsoft