commit | 4cd993e2ebeeba49468f485fda6b3e9b6f1cec7b | [log] [tgz] |
---|---|---|
author | Joel Stanley <joel@jms.id.au> | Mon Jun 20 18:57:41 2016 +0930 |
committer | Jeremy Kerr <jk@ozlabs.org> | Thu Jul 07 12:01:47 2016 +0800 |
tree | a5e4492fa56ac6320bc84a3a8109304fa63371c8 | |
parent | bcc4ffd0dccb984c25c1cfe0ed17ea296bbfef84 [diff] |
host-management: Add section on power control Signed-off-by: Joel Stanley <joel@jms.id.au>
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.md: 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
dbus-interfaces.md: Reference for APIs exposed to dbus
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