Hardware Management/FMFM: Difference between revisions

From OpenCompute
Jump to navigation Jump to search
Line 30: Line 30:
  <li>Coordinate with the broader OCP group to make sure there is a path for this general architecture</li>
  <li>Coordinate with the broader OCP group to make sure there is a path for this general architecture</li>
</ol>
</ol>
==Get Involved==
===Subproject Meets every other Tuesday from 7-9 am PST ===
: - [https://global.gotomeeting.com/join/454746381 Link to the Meeting]
:  - You can also dial in using your phone : United States: +1 (646) 749-3112 Access Code: 454-746-381
===Mailing List ===
Participate in the discussion:
: - FMFM on OCP Groups.io: [https://ocp-all.groups.io/g/OCP-HWMgt-FMFM FMFM Group Link]
: - [mailto:OCP-HWMgt-FMFM+subscribe@OCP-All.groups.io Subscribe to mailing list]
: - [mailto:OCP-HWMgt-FMFM@OCP-All.groups.io Post to mailing list]
=== Review and provide Feedback ===


===Documents===
===Documents===
[https://docs.google.com/document/d/1dtoKljPumGUYLGn1_2y22AdkLeohPL8sikfG18dDLDU/edit#heading=h.vrzhba2bazcv Link to Fleetscale Memory Fault Management (FMFM) Workstream Proposal on Google Drive]
[https://docs.google.com/document/d/1dtoKljPumGUYLGn1_2y22AdkLeohPL8sikfG18dDLDU/edit#heading=h.vrzhba2bazcv Link to Fleetscale Memory Fault Management (FMFM) Workstream Proposal on Google Drive]


===Past Fleetscale Memory Fault Management Events===
===Fleetscale Memory Fault Management Events===
* Coming Soon
* Coming Soon

Revision as of 15:21, 18 July 2023

Welcome to the OCP Fleetscale Memory Fault Management (FMFM) WIKI

Fleetscale Memory Fault Management is a Worksteam within the Hardware Management Project.

Hardware Management Project


Leadership

Scope

The FMFM is a workstream about standardization of Fleetscale Memory Fault Management

  • Proposed topics:
  1. Standardize vendor agnostic architecture for memory error handling
    1. Modularization of inputs from different hardware vendors
    2. APIs and connections between different modules from different vendors.
    3. Define the output of each module (failure cause, health information, RAS actions, etc.)
  2. Standardize memory error telemetry
    1. Format content for better fleet scale RAS management
    2. Troubleshooting, FRU replacement policies, etc.
  3. Coordinate with the broader OCP group to make sure there is a path for this general architecture

Get Involved

Subproject Meets every other Tuesday from 7-9 am PST

- Link to the Meeting
- You can also dial in using your phone : United States: +1 (646) 749-3112 Access Code: 454-746-381


Mailing List

Participate in the discussion:

- FMFM on OCP Groups.io: FMFM Group Link
- Subscribe to mailing list
- Post to mailing list


Review and provide Feedback

Documents

Link to Fleetscale Memory Fault Management (FMFM) Workstream Proposal on Google Drive

Fleetscale Memory Fault Management Events

  • Coming Soon