| commit | 6f933120f4700a269c3c1c0a4e7ddc920116fefe | [log] [tgz] |
|---|---|---|
| author | Patrick Venture <venture@google.com> | Mon May 20 10:16:41 2019 -0700 |
| committer | Patrick Venture <venture@google.com> | Tue Jun 18 09:10:08 2019 -0700 |
| tree | e7432406a6600d2c0858955eca3d21c8c78bfbdd | |
| parent | dfc4bbf2a227b2251ef8d69e7c88c8fbb2debaea [diff] |
firmware_update_via_blobs: new design notes about updating During implementation, it was observed that the exact moment of update wasn't sufficiently defined. This patchset defines that the moment the update is allowed upon closing of the verification blob once the verification state is "complete" and without "error." The exact implementation of update is specific to the type of image. There'll be a default implementation that simply starts a systemd unit "update-bmc.service". However, this is only one approach and the exact mechanism is up to the implementer. The default implementation will call the service. The service name will be configurable and the entire mechanism can be specified by providing another implementation of the interface. Similarly, to the verification mechanism. Signed-off-by: Patrick Venture <venture@google.com> Change-Id: I7bdc705c9a2589db3fe19ab19c764c6795fcc7be
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