commit | 6fc3db449e704d0f5a5afca728e9ac4facda7a91 | [log] [tgz] |
---|---|---|
author | Patrick Venture <venture@google.com> | Fri Oct 19 19:41:58 2018 -0700 |
committer | Patrick Venture <venture@google.com> | Thu Nov 01 12:27:31 2018 -0700 |
tree | e35a15c344eb2d2835e49506bc86d06f151f911c | |
parent | 00989a413d44586836b588347410ecc3d32b0522 [diff] |
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>
This repository contains documentation for OpenBMC as a whole. There may be component-specific documentation in the repository for each component.
These documents describe how to use OpenBMC, including using the programmatic interfaces to an OpenBMC system.
rest-api.md: Introduction to using the OpenBMC REST API
console.md: Using the host console
host-management.md: Performing host management tasks with OpenBMC
code-update: Updating OpenBMC and host platform firmware
These documents contain details on developing OpenBMC code itself
cheatsheet.md: Quick reference for some common development tasks
CONTRIBUTING.md: Guidelines for contributing to OpenBMC
kernel-development.md: Reference for common kernel development tasks
REST-cheatsheet.md: Quick reference for some common curl commands usage.
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