commit | e28e782ac960b36f0285bd52806185f59c31ad13 | [log] [tgz] |
---|---|---|
author | Jeremy Kerr <jk@ozlabs.org> | Tue Jan 09 13:07:16 2018 -0800 |
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | Tue Jan 09 18:06:00 2018 -0500 |
tree | 532781319afe85a7a66548077dfc7a86c023c402 | |
parent | 81d8a2fbf7966e62c283b0cefec9cf1c06899594 [diff] |
README: add Technical Steering Committee members Change-Id: If6f3c0ea2fb6e357c5f5c474776ce79d92161eb4 Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
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
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