commit | d070b7d7514062647b3f77c2c53bd74c226a3f5b | [log] [tgz] |
---|---|---|
author | Deepak Kodihalli <dkodihal@in.ibm.com> | Wed Jan 23 01:38:06 2019 -0600 |
committer | Gunnar Mills <gmills@us.ibm.com> | Tue Feb 05 20:48:04 2019 +0000 |
tree | 70a54c64c7bfbef1f8e82096c0d172212cfa39a2 | |
parent | 7273007d5bf677d9a17624d208095929082adc31 [diff] |
Add design for a PLDM stack Propose a design for implementing DMTF's Platform Level Data Model (PLDM) specifications. The idea is to employ PLDM for various "inside the box" communication scenarios, such as Host<->BMC, BMC<->Sensor device, BMC<->IO device, BMC<->BMC, etc. The design was first proposed on the OpenBMC mailing list: https://lists.ozlabs.org/pipermail/openbmc/2018-December/014356.html. Feedback received has been incorporated into this commit, and the plan is to continue further reviews on Gerrit. This commit describes, apart from the background and requirements, the design for elements such as the PLDM requester, PLDM responder, protocol handling, and platform specific actions. Change-Id: I8eb17e206a510f852d6035c5a15184646eeb540b Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.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