| commit | f3fe1216a9417dd4776a03881043984741a7fbae | [log] [tgz] |
|---|---|---|
| author | Patrick Venture <venture@google.com> | Wed Feb 13 08:36:10 2019 -0800 |
| committer | Patrick Venture <venture@google.com> | Wed Feb 13 11:59:08 2019 -0800 |
| tree | e8992ed77aa171ff6598b4571512bd845283959b | |
| parent | d55673e7fdb48fc17121bf45470b02e4c62df560 [diff] |
anti-patterns: explicit missing pkg messages Nearly all OpenBMC packages rely primarily on other OpenBMC packages to build and link. Therefore, it's generally sufficient to list the missing package via the default missing package behavior. In the event the package name isn't the same as the library expected, then overwriting the error message is still helpful. Change-Id: I9fc6eba07e09480f9e1da8662d202be681c7506e 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