[Twg] 2010-12-16 meeting minutes
John Carrier
carrier at cray.com
Thu Dec 16 19:41:40 UTC 2010
Attached are the minutes from today's meeting. I will post the new whitepaper draft shortly.
--jc
-------------- next part --------------
OpenSFS Technical Working Group
Meeting minutes : 12/16/2010
Concall: start : 9:30a PT, end : 10:32a PT)
Next meeting: Thursday, 1/6/2011 @ 9:30a PT/12:30p ET
Dial-in numbers are 715-726-4994 or 866-304-8294. The meeting ID and
password are 7012090.
Attending:
Name Organization email
----------------- -------------- ----------------------------
John Carrier Cray carrier at cray.com
Justin Miller Indiana Univ. jupmille at indiana.edu
Steve Simms Indiana Univ. ssimms at indiana.edu
Josh Walgenbach Indiana Univ. jjw at indiana.edu
Damian Hazen LBL dhazen at lbl.gov
Shay Seager OpenSFS ssseager at gmail.com
Andreas Dilger Oracle andreas.dilger at oracle.com
Dave Dillow ORNL dillowda at ornl.gov
Ercan Kamber RAID, Inc. ercan_kamber at raidinc.com
Robert Reed Whamcloud rread at whamcloud.com
Agenda:
* review the draft whitepaper
Discussion
The team thought the first draft captured the discussion at SC. We
surveyed individuals and the biggest hole was not addressing our
interaction with the other working groups in OpenSFS. We then went
through the document section by section. Shay mentioned the
need to address expected resource commitments from the member
companies. We addressed this idea in a new section.
Specific changes are described below:
Mission statement
- needed to be broader
- replace "I/O performance requirements" with "stability,
performance, and management requirements"
- remove reference to "Moore's law", although that is at the heart of
the imbalance between processors, memory, and storage performance.
Roadmap
- remove references to Oracle. OpenSFS is focused on the needs of
the HPC community. period.
- add text that requirements will come working with other working
groups in addition to the OpenSFS membership and Lustre community.
Feature Development
- add text to describing our intent to work with the other working
groups during the RFP process and require contractors to work with
them during integration.
Member Requirements -- new section
- to help scope time commitments, we defined the expected roles for
the following functions
- working group co-chairs
- RFP co-leads
- members
Meeting schedule
- no change
More information about the Twg
mailing list