Hardware Management/SpecsAndDesigns: Difference between revisions

From OpenCompute
Jump to navigation Jump to search
(29 intermediate revisions by 6 users not shown)
Line 2: Line 2:


This page contains links to the Specs ad Designs for the OCP Hardware Management Project
This page contains links to the Specs ad Designs for the OCP Hardware Management Project
=== OCP Redfish Profile ===
==== '''Baseline and Server profile''' ====
Under review ''(we plan to announce approved specs by [http://www.opencompute.org/ocp-u.s.-summit-2018/ OCP Summit 2018])''
* [http://files.opencompute.org/oc/public.php?service=files&t=6a94d2458bd8ade2fd7d6ac3937c5be4 OCP_Baseline_Hardware_Mgmt_v0.2.0.pdf]
* [http://files.opencompute.org/oc/public.php?service=files&t=aa88253da5dd70d5b5b965584a8943e6 OCP_Server_Mgmt_Interface_v0.2.0.pdf]
* ''(JSON files coming soon)''
==== '''Related documents [https://www.dmtf.org/standards/wip DMTF Work In Progress]''' ====
* [https://www.dmtf.org/sites/default/files/standards/documents/DSP2049_0.2.2b.pdf DSP2049 OCP Hardware Management with Redfish v0.2.2b 30 May 2017 (PDF)]
* [http://files.opencompute.org/oc/public.php?service=files&t=bb5d7c90ec35fa97759e065c5dbf5c38 Redfish OCP Profile xls]
* [http://files.opencompute.org/oc/public.php?service=files&t=c745936fcddec29ce2a08c6bf69ff75f OpenBMC Presentation]
* [http://files.opencompute.org/oc/public.php?service=files&t=e60b2f8bbcf6ebb615d19551f278345a Redfish OCP Profile pdf] ** Presented in mtg, Feb 21.
----


===LAVA LMP===
===LAVA LMP===
Line 7: Line 23:
More information about LAVA LMP can be found at:
More information about LAVA LMP can be found at:


* https://github.com/OCP-OpenComputeProject/lava-lmp-lmpd
* https://github.com/opencomputeproject/lava-lmp-firmware/subscription
* https://github.com/OCP-OpenComputeProject/lava-lmp-firmware
* https://github.com/opencomputeproject/lava-lmp-lmpd/subscription


===DRAFT of the Open Hardware Machine Management Specifications v1.01 (PDF)===


===DRAFT of the Open Hardware Machine Management Specifications v0.8 (PDF)===
OCP Hardware Management Specification: Remote Machine Management v1.01 Draft: 02-25-2014


OCP Hardware Management Specification: Remote Machine Management v0.8 Draft: 04-25-2012
* http://files.opencompute.org/oc/public.php?service=files&t=125cdfa0c090cb2106d8546f08561f6d
 
* http://files.opencompute.org/oc/public.php?service=files&t=2f8baef6b474fdcdc9d22c3e6db624a5


----
----
Line 34: Line 49:


----
----
===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.
The specifications allow a Data Center System Manager uniform remote access to the hardware in the rack. All the specifications have questions in red.
{| class="wikitable"
|+ OCP Specifications for IPMI
|-
! Specification
! Version
! Date
! Description
! License
|-
| [http://files.opencompute.org/oc/public.php?service=files&t=3158cab091d0dbd1c4c283a32c7c26f7 OCP ID]
| 0.04
| June 9, 2014
| Identify all OCP specifications implemented by a single IPM Controller
| OWFa 1.0
|-
| [http://files.opencompute.org/oc/public.php?service=files&t=7e7ae048c1da42ae73f34231759dcebf ICAP Base]
| 0.02
| June 9, 2014
| The basic functions of an OCP IPM Controller that a Data Center System Manager depends on
| OWFa 1.0
|-
| [http://files.opencompute.org/oc/public.php?service=files&t=c56cbe48527af22e1d9a25f6603edcff ICAP OPTI]
| 0.02
| June 9, 2014
| The identification of XFSP+/QSFP bays and protocol independent monitoring of optical links for XSFP+/QSFP modules
| OWFa 1.0
|-
| [http://files.opencompute.org/oc/public.php?service=files&t=cf741bcdea44720674b98a6f12937db2 ICAP DRAM]
| 0.03
| June 9, 2014
| The identification and temperature monitoring of DDR3/DDR4 modules
| OWFa 1.0
|}
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.

Revision as of 20:40, 29 January 2018

Specs and Designs

This page contains links to the Specs ad Designs for the OCP Hardware Management Project

OCP Redfish Profile

Baseline and Server profile

Under review (we plan to announce approved specs by OCP Summit 2018)

Related documents DMTF Work In Progress


LAVA LMP

More information about LAVA LMP can be found at:

DRAFT of the Open Hardware Machine Management Specifications v1.01 (PDF)

OCP Hardware Management Specification: Remote Machine Management v1.01 Draft: 02-25-2014


Charter for the Open Hardware Management Track (PDF)

Charter for Open Hardware Management Track Draft: 12-28-2011


DRAFT Charter for Open Hardware Management Track w/Japanese Translation (PDF)

Proposed track for Open Hardware Management


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. The specifications allow a Data Center System Manager uniform remote access to the hardware in the rack. All the specifications have questions in red.

OCP Specifications for IPMI
Specification Version Date Description License
OCP ID 0.04 June 9, 2014 Identify all OCP specifications implemented by a single IPM Controller OWFa 1.0
ICAP Base 0.02 June 9, 2014 The basic functions of an OCP IPM Controller that a Data Center System Manager depends on OWFa 1.0
ICAP OPTI 0.02 June 9, 2014 The identification of XFSP+/QSFP bays and protocol independent monitoring of optical links for XSFP+/QSFP modules OWFa 1.0
ICAP DRAM 0.03 June 9, 2014 The identification and temperature monitoring of DDR3/DDR4 modules OWFa 1.0

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:

  1. General: general firmware update requirements
  2. Security: requirements related to the integrity and authenticity of the image
  3. Control: requirements related to how firmware updates are controlled
  4. Status: requirements related to how/what status is available

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.

Cloud Server Multi Node System Specification version V0.7.5, Date August 19,2015 PDF


Miscellaneous Files