The following Scope Statement applies to the 2.5 Release project. Lustre feature releases follow a release train model, with feature releases targeted every 6 months. 

Problem statement

Lustre 2.5 is planned to be a regular feature release as a follow-on to Lustre 2.4 which was made generally available (GA) on 2013-05-31. There are several new features, improvements, and bug fixes that have been, or are currently being developed for landing to the Lustre Master branch. Lustre 2.5 will use the train model approach where only those features landed prior to the Feature Freeze Date (2013-07-31) will be included in the release. 

Project goals

In addition to the goals listed in the Problem Statement, the goals listed below are being added for the Lustre 2.5 release:

In Scope

Since the Lustre Feature releases are being managed using the train model, there are often many more proposed features than will make it into any one release. Below is a listing of all known features that are possible candidates for inclusion in 2.5 given the timing of the 2.5 feature freeze date. 


Proposed Features & Enhancements (Developing Organization)

The following are Candidate Features for Lustre 2.5:


Bug Blocker List:

2.5 Bug Blocker List:

Out of Scope

The following items are considered out of scope for the Lustre 2.5 release:

Kernel Versions/OFED Versions/e2fsprogs Versions: 

Upgrades submitted after the Feature Freeze date will be considered on a case by case basis

Server Kernel Version:  

2.6.32-358.6.2.el6 (RHEL6.4)

Client Kernel Versions:  

2.6.32-358.6.2.el6 (RHEL6.4)



OFED Versions:

o2iblnd - OFED 1.5.4

e2fsprogs Version:


Project Constraints

Project Constraints are boundaries that have been defined which affect how the project can be delivered. Constraints are non-negotiable elements of the project. The identified constraints for the Lustre 2.5 release are:

Key Deliverables and Milestones

Baseline Test Plan:  2013-05-31

Feature Freeze: 2013-07-31

Code Freeze:  2013-09-30

2.5 Release GA:  2013-10-31