[Twg] requirements document update
John Carrier
carrier at cray.com
Fri Apr 20 07:05:18 UTC 2012
During the TWG concall this morning, we walked through the comments several reviewers had made to our 2012 requirements document. Several of us spent the rest of the day editing the text and resolving the remaining comments (thanks, Alex, Andreas, Cory, Josh and Nathan!)
It's now your opportunity to review the document (http://goo.gl/63u9Q) to help us select the requirements we will recommend to the OpenSFS Board for development in 2013.
As we did last year, we need to create a short list of 4-5 items we think are most important to the Lustre community. The OpenSFS Board must agree with our recommendation before we can pursue proposals to meet these requirements.
Now that we have finished gathering requirements, the first step is for community members to send their top 10 requirements from the list below in priority order to discuss at lists.opensfs.org<mailto:discuss at lists.opensfs.org>. We will discuss how to resolve our lists and make the recommendation to the board at the TWG face to face meeting (Weds 4/25 after LUG in Austin).
Please send questions or comments to the discuss at lists.opensfs.org<mailto:discuss at lists.opensfs.org> reflector.
--jc
The following table summarizes the 31 gathered requirements described in our document (http://goo.gl/63u9Q). Category definitions are only meant to help organize requirements for discussion. There is no significance to the order in which the requirements are listed.
Category
Requirement
Performance
Single client performance
Single shared file performance
Quality of service
Locality and scalability
Availability
Scalable fault management
Avoid RPC timeouts
Manageability and Administrative
Better support for newer kernels
Improved configuration robustness
Administrative shutdown
Better userspace tools
Snapshots
Arbitrary OST assignment
Storage Management
HSM and storage management infrastructure
OST migration/rebalancing
Asynchronous file replication (mirroring)
Complex file layouts
Dynamic layout for subset of a file
Storage pool quotas
Unified storage target
LNET
IPv6
Dynamic LNET configuration
Improved LNET robustness
LNET channel bonding
Application Interface
Improved storage semantics/interfaces
Better user tool API
POSIX extensions for file sets
POSIX extensions for scalable opens
Other
Varying page-sizes
Mixed endian support
Improved security infrastructure
Improved Lustre Tests
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensfs.org/pipermail/twg_lists.opensfs.org/attachments/20120420/6f5eafdb/attachment.html>
More information about the Twg
mailing list