Difference between revisions of "Hardware Management/SpecsAndDesigns"

From OpenCompute
Jump to: navigation, search
m (Baseline and Server profile)
(Baseline and Server profile)
Line 7: Line 7:
==== '''Baseline and Server profile''' ====
==== '''Baseline and Server profile''' ====
Under review ''(announced at [http://www.opencompute.org/ocp-u.s.-summit-2018/ OCP Summit 2018])''
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=6a94d2458bd8ade2fd7d6ac3937c5be4 OCP_Baseline_Hardware_Mgmt_v0.2.0.pdf]
* [http://files.opencompute.org/oc/public.php?service=files&t=cd62c39f58921c7eb83bee51bee8cbc5 Comments.pdf] received during review period
** JSON file: [http://files.opencompute.org/oc/public.php?service=files&t=84541cf163144917875e9922b1c07318 OCPBaselineHardwareManagement.v0_2.json]
* [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]
* [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=2b0c0dbc13d950a363a8883fb8e68f50 OCPServerHardwareManagement.v0_2.json]
** JSON file: [http://files.opencompute.org/oc/public.php?service=files&t=ae8f671f43c454bf29caeaaf6e7770b3 OCPServerHardwareManagement.v0_2_1.json] (updated)
==== '''Related documents [https://www.dmtf.org/standards/wip DMTF Work In Progress]''' ====
==== '''Related documents [https://www.dmtf.org/standards/wip DMTF Work In Progress]''' ====

Revision as of 09:32, 17 April 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 (announced at OCP Summit 2018)

Related documents DMTF Work In Progress


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