commit | a493305a34257aadd30a261d42996563ba9669aa | [log] [tgz] |
---|---|---|
author | Gunnar Mills <gmills@us.ibm.com> | Thu Jan 24 14:47:23 2019 -0600 |
committer | Gunnar Mills <gmills@us.ibm.com> | Mon Jan 28 14:35:47 2019 +0000 |
tree | dff48f0f6fcf024c51f315c24c388ad97f51ae93 | |
parent | 1b56459b545bb860321da9a70db275cde2eb3850 [diff] |
REST-cheatsheet: Remove unnecessary write to cjar "-c, --cookie-jar <filename> (HTTP) Specify to which file you want curl to write all cookies after a completed operation. Curl writes all cookies from its in-memory cookie storage to the given file at the end of operations. If no cookies are known, no data will be written." Only login and logout write to the cookie file. Removed to not confuse people, also makes the commands shorter and easier to read. Tested: Issued curl commands like "Host power on" and enumerate software. Change-Id: I2b9a494758014edd5ca0c4173db6eaec78e7c1ae 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.
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