| commit | 6c5f280f5b9cacb0c5a80ad81ef9f63cf37d6aa3 | [log] [tgz] |
|---|---|---|
| author | Gunnar Mills <gmills@us.ibm.com> | Fri Dec 06 10:39:20 2019 -0600 |
| committer | Gunnar Mills <gmills@us.ibm.com> | Mon Dec 09 18:31:51 2019 +0000 |
| tree | 0e6aaf05b3e53dab2fc15ed8574179f704f88ae0 | |
| parent | 9a71ea19d19a88640f8c8ab364adfff91a19e8b9 [diff] |
Remove meetings/ Although a really neat idea, meetings/ is not used and contains wrong information. meetings.yaml still has the canceled OpenBMC Community Meeting. https://gerrit.openbmc-project.xyz/c/openbmc/docs/+/24826 removed the meetings.ics for the OpenBMC Community Meeting but left meetings.yaml. No other workgroups have added their meetings. Meetings have been tracked via the mailing list or wiki. Overall, the project is moving towards more IRC and mailing list and fewer in-person meetings. More information on IRC and the mailing list: Mail: openbmc@lists.ozlabs.org https://lists.ozlabs.org/listinfo/openbmc IRC: #openbmc on freenode.net Change-Id: Ie73172f27ec2207eb7a22dbb6acea81254b5d54f Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
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