Wear Monitor: Difference between revisions
(→Agenda) |
m (→Meetings) |
||
Line 15: | Line 15: | ||
Subject: OCP Storage Wear Monitor | Subject: OCP Storage Wear Monitor | ||
Date: Thu, Apr 14 2016 | Date: Thu, Apr 14 2016 | ||
Start Time: 6:00 PM ( | Start Time: 6:00 PM (MDT)5:00 PM (PDT) | ||
End Time: 7:00 PM ( | End Time: 7:00 PM (MDT) 6:00 PM (PDT) | ||
Meeting ID 30807354 | Meeting ID 30807354 | ||
Revision as of 20:35, 14 April 2016
WELCOME
- Welcome to the OCP Wear Monitor Working Group.
Get Involved
Events
The schedule for events pertaining to the Wear Monitor Working Group will be posted here.
Meetings
This is where the schedule for Wear Monitor meetings will be posted. This call is open to the public.
Subject: OCP Storage Wear Monitor Date: Thu, Apr 14 2016 Start Time: 6:00 PM (MDT)5:00 PM (PDT) End Time: 7:00 PM (MDT) 6:00 PM (PDT) Meeting ID 30807354
Meeting URL:
https://www.fuzemeeting.com/fuze/76a85d4f/30807354
You can find international access numbers at: https://www.fuze.com/extras/symphony Toll Free # +18553463893 Toll Number +12014794595
Agenda
Coolan Use Case for wear monitor - Amir Michael
Open Discussion on Wear Monitor ideas and ways to progress
Should we leverage other frameworks that already exist?
For example there is a project called SNAP: https://github.com/intelsdi-x/snap that already has many plug-ins both for collecting and publishing telemetry. One plug-in collector gathers SMART data from Intel SSDs: https://github.com/intelsdi-x/snap-plugin-collector-smart
Communication
- Mailing List - opencompute-storage@lists.opencompute.org
- Website - Wear Monitor Wiki (this page)
Specs and Designs
- Links to Current specs and designs -