Editing Hardware Management/SpecsAndDesigns
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 5: | Line 5: | ||
=== OCP Redfish Profile === | === OCP Redfish Profile === | ||
==== '''Baseline and Server profile''' ==== | |||
Under review ''(announced at [http://www.opencompute.org/ocp-u.s.-summit-2018/ OCP Summit 2018])'' | |||
* [http://files.opencompute.org/oc/public.php?service=files&t=cd62c39f58921c7eb83bee51bee8cbc5 Comments.pdf] received during review period | |||
* [http://files.opencompute.org/oc/public.php?service=files&t=7f0aac1807e0c6194c06f5826f126213 OCP_Baseline_Hardware_Mgmt_v0.2.1.pdf] (previous: [http://files.opencompute.org/oc/public.php?service=files&t=6a94d2458bd8ade2fd7d6ac3937c5be4 v0.2.0]) | |||
** JSON file: [http://files.opencompute.org/oc/public.php?service=files&t=c1ffe868a3d58619525699c00c2a75e4 OCPBaselineHardwareManagement.v0_2_1.json] (updated) | |||
* [http://files.opencompute.org/oc/public.php?service=files&t=aa88253da5dd70d5b5b965584a8943e6 OCP_Server_Mgmt_Interface_v0.2.0.pdf] | |||
** JSON file: [http://files.opencompute.org/oc/public.php?service=files&t=ae8f671f43c454bf29caeaaf6e7770b3 OCPServerHardwareManagement.v0_2_1.json] (updated) | |||
{| class="wikitable" | {| class="wikitable" | ||
|+ style="text-align: left" | Related documents | |+ style="text-align: left" | Related documents | ||
|- | |- | ||
! | ! Specification | ||
! Version | ! Version | ||
! Date | ! Date | ||
Line 64: | Line 27: | ||
| - | | - | ||
| - | | - | ||
| Collection of DMTF work in progress, and the official | | Collection of DMTF work in progress, and the official SPMF Redfish repository | ||
| - | |||
|- | |||
| [https://www.dmtf.org/sites/default/files/standards/documents/DSP2049_0.2.2b.pdf DSP2049 (PDF)] | |||
| v0.2.2b | |||
| 30 May 2017 | |||
| OCP Hardware Management with Redfish (proposed spec) | |||
| - | | - | ||
|- | |- | ||
Line 73: | Line 42: | ||
| - | | - | ||
|- | |- | ||
| [http://files.opencompute.org/oc/public.php?service=files&t=e60b2f8bbcf6ebb615d19551f278345a Redfish OCP Profile] | | [http://files.opencompute.org/oc/public.php?service=files&t=e60b2f8bbcf6ebb615d19551f278345a Redfish OCP Profile (PDF Presentation)] | ||
| v1 | | v1 | ||
| Feb 21, 2017 | | Feb 21, 2017 | ||
| Presentation to the HW Management group meeting | | Presentation to the HW Management group meeting Feb 21, 2017 | ||
| - | | - | ||
|- | |- | ||
| [http://files.opencompute.org/oc/public.php?service=files&t=c745936fcddec29ce2a08c6bf69ff75f OpenBMC (PDF Presentation)] | |||
| [http://files.opencompute.org/oc/public.php?service=files&t=c745936fcddec29ce2a08c6bf69ff75f OpenBMC] | |||
| - | | - | ||
| Nov 17, 2016 | | Nov 17, 2016 | ||
| Presentation to the HW Management group meeting | | Presentation to the HW Management group meeting Feb 21, 2017 | ||
| - | | - | ||
|} | |} | ||
===LAVA LMP=== | |||
More information about LAVA LMP can be found at: | |||
* https://github.com/opencomputeproject/lava-lmp-firmware/subscription | |||
* https://github.com/opencomputeproject/lava-lmp-lmpd/subscription | |||
===DRAFT of the Open Hardware Machine Management Specifications v1.01 (PDF)=== | |||
OCP Hardware Management Specification: Remote Machine Management v1.01 Draft: 02-25-2014 | |||
== | * http://files.opencompute.org/oc/public.php?service=files&t=125cdfa0c090cb2106d8546f08561f6d | ||
---- | |||
=== Charter for the Open Hardware Management Track (PDF)=== | |||
Charter for Open Hardware Management Track Draft: 12-28-2011 | |||
* http://files.opencompute.org/oc/public.php?service=files&t=ad23158efca9a37e704046e3cbfdc209 | |||
---- | ---- | ||
===DRAFT Charter for Open Hardware Management Track w/Japanese Translation (PDF)=== | |||
Proposed track for Open Hardware Management | |||
* http://files.opencompute.org/oc/public.php?service=files&t=537a0c1930f02319509930768b23c6c3 | |||
* | |||
---- | ---- | ||
===DRAFT Hardware Management Specifications for IPMI | ===DRAFT Hardware Management Specifications for IPMI=== | ||
Proposed specifications for the IPMI implementation on any device using IPMI. This includes PDUs, Servers, Switches and Storage devices. | Proposed specifications for the IPMI implementation on any device using IPMI. This includes PDUs, Servers, Switches and Storage devices. | ||
Line 173: | Line 127: | ||
As Data Centers raise room temperatures, potentially on a daily basis, the ICAP OPTI and ICAP DRAM provide feedback on how close the hardware is to the manufacturer define thermal limits. | As Data Centers raise room temperatures, potentially on a daily basis, the ICAP OPTI and ICAP DRAM provide feedback on how close the hardware is to the manufacturer define thermal limits. | ||
---- | ---- | ||
===DRAFT Requirements for Firmware Update=== | |||
The draft specification identifies the firmware update requirements that all OCP compliant platforms and devices must adhere to. | |||
The Firmware Update solution is for the application the user interfaces and the capabilities of the embedded firmware on the servers, switches and storage devices. | |||
The requirements are broken into four sections: | |||
# General: general firmware update requirements | |||
# Security: requirements related to the integrity and authenticity of the image | |||
# Control: requirements related to how firmware updates are controlled | |||
# Status: requirements related to how/what status is available | |||
[http://files.opencompute.org/oc/public.php?service=files&t=c3ee8db5c9e64c1ddecc71fe084afaf0 Firmware Update Requirements version 0.2b PDF] | |||
---- | |||
===Cloud Server Multi Node System Specification=== | |||
A description and requirements of a Cloud Server which is either a server, enclosure or rack that contains other uniquely addressable and managable devices. | |||
The document's purpose is to have a single Ethernet connection to the Cloud Server and document the possible bus architectures, managment protocols and minimum expected functionality of the Nodes contained in the Cloud Server. | |||
The Clould Server's BMC with a Ethernet connection to the outside world is the called the Spine BMC and IPMI RMCP or RESTfull protocols are allowed. Internally the Spine BMC communicates to the Node using SMBus and GPIO which determines Node presence, Node power control and ALERT signaling. | |||
The Node requirements include a subset of the IPMI 2.0 commands. The Spine BMC may have a Serial Console session to each Node. | |||
[http://files.opencompute.org/oc/public.php?service=files&t=1eb58f54e79a48f0007de6b7379a093f Cloud Server Multi Node System Specification version V0.7.5, Date August 19,2015 PDF] | |||
===Miscellaneous Files=== | |||
* [http://files.opencompute.org/oc/public.php?service=files&t=64189159f78d34e4da0a9165d2a18ee0 PLDM for FW Updates PPTX] - presented by Yuval Itkin, Sept 19 mtg. |