Editing RAS API Workstream
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 15: | Line 15: | ||
Having no industry standard for RAS management makes each HW vendor solution specific and resource intensive; while delaying RAS feature adoption. <br /> | Having no industry standard for RAS management makes each HW vendor solution specific and resource intensive; while delaying RAS feature adoption. <br /> | ||
When creating a specification to solve the standardization problem some major pain points need to be considered: | When creating a specification to solve the standardization problem some major pain points need to be considered: | ||
* Specification for common '''abstraction''' for RAS between software and hardware that is '''vendor agnostic''' as well as '''platform agnostic'''. | * Specification for common '''abstraction''' for RAS between software and hardware that is '''vendor agnostic''' as well as '''platform agnostic'''. | ||
* Connectivity for RAS management should allow '''co-existence''' of In Band and Out of Band methods | * Connectivity for RAS management should allow '''co-existence''' of In Band and Out of Band methods | ||
| Line 26: | Line 24: | ||
The current baseline is [https://docs.google.com/document/d/1LhGtwIdhw7XuH84rPfRRq8grhl-fsIN1/edit?usp=share_link&ouid=115560947677973489092&rtpof=true&sd=true Revision 0.8]. We plan to meet with companies that agree with this objective in order to draft a complete specification that solves the problem statement. | The current baseline is [https://docs.google.com/document/d/1LhGtwIdhw7XuH84rPfRRq8grhl-fsIN1/edit?usp=share_link&ouid=115560947677973489092&rtpof=true&sd=true Revision 0.8]. We plan to meet with companies that agree with this objective in order to draft a complete specification that solves the problem statement. | ||
==Workstream Leadership== | ==Workstream Leadership== | ||
:- [mailto:acwalton@google.com Drew Walton] (Google), [mailto:antonio.j.hasbun.marin@intel.com Antonio Hasbun] (Intel) | |||
==Get Involved== | ==Get Involved== | ||
The process to join the workstream is as follows: | The process to join the workstream is as follows: | ||
<br /> | |||
# Join the mailing list: [mailto:OCP-RAS-API+subscribe@OCP-All.groups.io OCP-RAS-API+subscribe@OCP-All.groups.io] | |||
# Join the [https://drive.google.com/drive/folders/0AKz7Api2DyIRUk9PVA Google drive] This will grant you access to the Google drive for the workstream and we can download and get the CLA signed | |||
<br/> | |||
This is a link to the CLA that needs to be signed in order to participate in the workstream. [https://docs.google.com/document/d/1LhGtwIdhw7XuH84rPfRRq8grhl-fsIN1/edit?usp=share_link&ouid=115560947677973489092&rtpof=true&sd=true RAS API CLA ] | |||
<br /> | |||
===Workstream Meets every TBD === | |||
: - [https://global.gotomeeting.com/join/ Link to the Meeting] | |||
: - You can also dial in using your phone : US (Toll Free): 1 877 309 2073 / US: +1 (646) 749-3129 - (Access Code: ) | |||
===Mailing List === | ===Mailing List === | ||
Participate in the discussion, mailing list: OCP-RAS-API@OCP-All.groups.io [https://ocp-all.groups.io/g/OCP-RAS-API Mailing List Info] | |||
==Links to Documents== | ==Links to Documents== | ||
===[https://drive.google.com/drive/folders/0AKz7Api2DyIRUk9PVA Work in Progress Documents Folder]:=== | |||
===Presentations & Other Documents=== | ===Presentations & Other Documents=== | ||
OCP Presentation Template - please contact [mailto:michael@opencompute.org Michael Schill] or [mailto:archna@opencompute.org Archna Haylock] for a copy | |||
==Past Meeting Recordings== | |||