Lustre Community Development in Progress: Difference between revisions

From OpenSFS Wiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
[[Category:LWG]]
[[Category:LWG]]
== Lustre Development Scope ==
For the Lustre development cycle, we are tracking all outstanding work for the release right in Jira.  We do so by adding a version string (e.g. "Lustre 2.6.0") to the "Fix Version/s" field of any ticket that we have scoped to be part of that release.  Jira uses the "Fix Version/s" field in a number of ways, including its built-in Road Map, Change Log, and of course Issues pages.
Thanks to use of this field, the Lustre project page in Jira will better reflect the state of development for the next Lustre release.  Here are some quick links:
* [https://jira.hpdd.intel.com/browse/Jira LU Lustre Project Page]
* [[Jira LU Keywords]]
* [https://jira.hpdd.intel.com/browse/LU/fixforversion/10595 Lustre 2.6.0 Jira Summary Page]
* [https://jira.hpdd.intel.com/issues/?jql=fixVersion%20%3D%20%22Lustre%202.8.0%22%20AND%20project%20%3D%20LU%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC Lustre 2.8.0 Unresolved Issues]
General release info (scope, schedule, etc.) is tracked on per-version LWG pages:
* [[Lustre_2.6.0|Lustre 2.6]]
* [[Lustre_2.7.0|Lustre 2.7]]
* [[Lustre_2.8.0|Lustre 2.8]]
Keep in mind that the list of work is not static.  As bugs are discovered, the list will grow.  When new Jira tickets are opened for Lustre bug on the master branch, Intel, as part of the work for the [[Community Tree Development Contract]], will make the initial determination of whether the ticket should be added to the scope for a release.
If a party feels like a ticket should be added to the Lustre version scope, but Intel did not make that initial determination, a request to have the version (e.g. "Lustre 2.6.0") added to the "Fix Version/s" field should be made in the Jira ticket itself.
Should Intel and the interested party disagree, the issue should be raised on [[Lustre Working Group]] [http://lists.opensfs.org/listinfo.cgi/lwg-opensfs.org mailing list] so that the issue can be discussed by the larger community and final determination made.
= List of features under development =
Features that are currently being developed for future Lustre releases. Features are not listed in priority or landing order.  Projects not currently under development, or ideas for features, should be listed on the Project Ideas page.
Features that are currently being developed for future Lustre releases. Features are not listed in priority or landing order.  Projects not currently under development, or ideas for features, should be listed on the Project Ideas page.


Line 64: Line 38:
| Lock ahead || Allow user space to request LDLM extent locks in advance of need.  Intended to optimize shared file IO. || Patrick Farrell (Cray) || [https://jira.hpdd.intel.com/browse/LU-6179 LU-6179] || ?? || .
| Lock ahead || Allow user space to request LDLM extent locks in advance of need.  Intended to optimize shared file IO. || Patrick Farrell (Cray) || [https://jira.hpdd.intel.com/browse/LU-6179 LU-6179] || ?? || .
|}
|}
Again, please note that the targeted release information is provided by the developing organization for informational purposes only and is in no way a roadmap commitment.
[[File:LustreRoadmap.png|640px|link=http://lustre.opensfs.org/community-lustre-roadmap]|Lustre Community Roadmap]]

Revision as of 17:52, 5 March 2015

Features that are currently being developed for future Lustre releases. Features are not listed in priority or landing order. Projects not currently under development, or ideas for features, should be listed on the Project Ideas page.

Please note that the targeted completion date information is provided by the developing organization for informational purposes only and is in no way a roadmap commitment.

Feature Feature Summary Point of Contact Tracker Target Date (YYYY-MM) Landed Release
Patchless Server Remove Lustre kernel patches to allow Lustre servers to be more easily ported to new kernels, and to be built against vendor kernels without changing the vendor kernel RPMs. ? (Intel) LU-20 2016-02 .
End-to-End Data Integrity with T10 Add a path to pass T10 Protection Information from Lustre clients through to server disks to reduce CPU overhead of multiple checksum calculations. ? (Xyratex) LU-2488 LU-2584 2016-02 .
LFSCK Phase 3 - DNE consistency Enhance LFSCK to work with DNE filesystems, including remote directory entries, and OST orphan handling for multiple MDTs. Richard Henwood (Intel) LU-2307 2015-02 .
DNE Phase IIb Asynchronous Commit of cross-MDT updates for improved performance. Remote rename and remote hard link functionality. Richard Henwood (Intel) LU-3534 2015-02 .
Layout Enhancement Add support for multiple layouts on a single file, for File Level Replication, Data on MDT, extent-based layouts, etc. Intel LU-3480 2015-08 .
File Level Replication Phase 1 Solution Architecture and HDL, Exclusive Open, RAID 1 Layout, Layout Modification Method, Read Only RAID 1 ? (Intel) LU-3254 2016-02 .
File Level Replication Phase 2 Immediate asynchronous write from client. ? (Intel) LU-3254 2016-08 .
Data on MDT Allow small files to be stored directly on the MDT for reduced RPC count and improved performance. ? (Intel) . 2016-02 .
Dynamic LNET Config Introduces a user space script which will read routes from a config file and add those routes to LNET dynamically with the lctl utility. This allows the support of very large routing tables Amir Shehata (Intel) LU-2456 2015-02 .
Quota for Projects Allow specifying a "project" or "subtree" identifier for files for accounting to a project, separate from UID/GID. Shuichi Ihara (DDN) LU-4017 2015-08 .
Large Bulk IO Increase the OST bulk IO maximum size to 16MB or larger for more efficient disk IO submission. ? (Intel/DDN) . 2016-02 .
Kerberos Revival Fix up existing Kerberos code so it is tested working again. ? (Xyratex) . 2015-08 .
UID/GID mapping Map UID/GID for remote client nodes to local UID/GID on the MDS and OSS. Allows a single Lustre filesystem to be shared across clients with administrative domains. Stephen Simms (Indiana University) LU-3527 2015-02 .
Shared Key Crypto Allow node authentication and/or RPC encryption using symmetric shared key crypto with GSSAPI. Avoids complexity in configuring Kerberos across multiple domains. Stephen Simms (Indiana University) LU-3289 2016-02 .
Lock ahead Allow user space to request LDLM extent locks in advance of need. Intended to optimize shared file IO. Patrick Farrell (Cray) LU-6179 ?? .