| commit | 199173c6f0f94ec64ad4ef3f22e4fbd6e2fbdafa | [log] [tgz] |
|---|---|---|
| author | Patrick Venture <venture@google.com> | Wed Jun 19 12:06:05 2019 -0700 |
| committer | Patrick Venture <venture@google.com> | Thu Jun 27 14:05:14 2019 +0000 |
| tree | 618852e6897143587b9fddb1ac0548c4b1deb86f | |
| parent | 76e35b3d642e21fd9762c0f7b27ff36ea2c43409 [diff] |
designs: firmware_update_via_blobs: Add notion of cleanup blob Add the notion of a cleanup blob id that is present. This was invented as a convenience mechanism for wiping the BMC's update artifacts on failure. On memory constrained systems, having a 32MiB file sitting in the RAM FS is wasteful on failure. One can simply reboot the BMC to address this, and therefore this blob is only a convenience. Deleting the artifacts on failure is not a default behavior because they are meant to be harmless. This also allows a developer to use unsigned images if they want without requiring a different update mechanism. The developer would require console access, but with that access could flash the "invalid" image if they chose. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: Ie1bc184d24295ed61fd8be8fd48fb50c205235ac
This repository contains documentation for OpenBMC as a whole. There may be component-specific documentation in the repository for each component.
The features document lists the project's major features with links to more information.
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