Difference between revisions of "Hardware Management/SpecsAndDesigns"

From OpenCompute
Jump to: navigation, search
m (DRAFT Charter for Open Hardware Management Track w/Japanese Translation (PDF))
(Baseline and Server profile)
 
(6 intermediate revisions by the same user not shown)
Line 35: Line 35:
 
| OWFa 1.0
 
| OWFa 1.0
 
|}
 
|}
 
 
 
{| class="wikitable"
 
{| class="wikitable"
 
|+ style="text-align: left" | Related documents
 
|+ style="text-align: left" | Related documents
Line 50: Line 48:
 
| -
 
| -
 
| Collection of DMTF work in progress, and the official DMTF Redfish Forum repository
 
| Collection of DMTF work in progress, and the official DMTF Redfish Forum 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 68: Line 60:
 
| Feb 21, 2017
 
| Feb 21, 2017
 
| Presentation to the HW Management group meeting Feb 21, 2017
 
| Presentation to the HW Management group meeting Feb 21, 2017
 +
| -
 +
|-
 +
|-
 +
| [https://drive.google.com/file/d/1xmMNm3_wSkIKsJL-U1Biw0xuflTxCCLY Redfish Conformance Test Suite]
 +
| -
 +
| Nov 2018
 +
| Presentation to the HW Management group meeting
 
| -
 
| -
 
|-
 
|-
Line 79: Line 78:
 
----
 
----
  
===LAVA LMP===
+
===DRAFT Requirements for Firmware Update===
  
More information about LAVA LMP can be found at:
+
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
  
* https://github.com/opencomputeproject/lava-lmp-firmware/subscription
+
[http://files.opencompute.org/oc/public.php?service=files&t=c3ee8db5c9e64c1ddecc71fe084afaf0 Firmware Update Requirements version 0.2b PDF]
* https://github.com/opencomputeproject/lava-lmp-lmpd/subscription
+
----
  
===DRAFT of the Open Hardware Machine Management Specifications v1.01 (PDF)===
+
===Cloud Server Multi Node System Specification===
  
OCP Hardware Management Specification: Remote Machine Management v1.01 Draft: 02-25-2014
+
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.  
  
* http://files.opencompute.org/oc/public.php?service=files&t=125cdfa0c090cb2106d8546f08561f6d
+
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.
  
=== Old Charter for the Open Hardware Management Track (PDF)===
+
[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]
  
Old Charter for Open Hardware Management Track Draft: 12-28-2011
+
----
 
+
===Presentations===
* http://files.opencompute.org/oc/public.php?service=files&t=ad23158efca9a37e704046e3cbfdc209
+
* [https://146a55aca6f00848c565-a7635525d40ac1c70300198708936b4e.ssl.cf1.rackcdn.com/images/94f8a3478db56eef7e8868159d193633c0116938.pdf OCP Profiles for Hardware Management] - presented by Hemal Shah and John Leung, OCP Global Summit 2019.
 +
* [https://146a55aca6f00848c565-a7635525d40ac1c70300198708936b4e.ssl.cf1.rackcdn.com/images/efcddf341fa55a63177c0180152f6d59ed23449e.pdf PMCI Standards for Hardware Management] - presented by Hemal Shah and Patrick Caporale, OCP Global Summit 2019.
  
 
----
 
----
  
===DRAFT Old Charter for Open Hardware Management Track w/Japanese Translation (PDF)===
+
===Links to Open Source Projects===
 
+
* [https://en.wikipedia.org/wiki/OpenBMC Link to OpenBMC]
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 (Legacy)===
  
 
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 151: Line 155:
 
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.
 
 
===Links to Open Source Projects===
 
* [https://en.wikipedia.org/wiki/OpenBMC Link to OpenBMC]
 

Latest revision as of 06:41, 20 April 2019

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

Specs under review (announced at OCP Summit 2018)

Specs under review
Specification Version Date Description License
Comments 20180417.pdf v2 - Comments received during review period; specifically HW Management meeting April 17, 2018 -
Baseline Profile - (JSON) Spec:v1.0, JSON:v1.0 April 18, 2018 OCP Redfish Profile - Baseline Hardware Management specification, and JSON schema OWFa 1.0
Server Profile - (JSON) Spec:v0.2.1, JSON:v0.2.3 April 18, 2018 OCP Redfish Profile - Server Hardware Management extensions, and JSON schema OWFa 1.0
Related documents
Specification Version Date Description License
DMTF WIP and DMTF Redfish - - Collection of DMTF work in progress, and the official DMTF Redfish Forum repository -
Redfish OCP Profile (XLS) v0.5 June 1, 2016 Mapping Redfish properties to OCP requirements (initial worksheet) -
Redfish OCP Profile (PDF Presentation) v1 Feb 21, 2017 Presentation to the HW Management group meeting Feb 21, 2017 -
Redfish Conformance Test Suite - Nov 2018 Presentation to the HW Management group meeting -
OpenBMC (PDF Presentation) - Nov 17, 2016 Presentation to the HW Management group meeting Feb 21, 2017 -

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


Presentations


Links to Open Source Projects


DRAFT Hardware Management Specifications for IPMI (Legacy)

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.