WARNING: This is the _old_ Lustre wiki, and it is in the process of being retired. The information found here is all likely to be out of date. Please search the new wiki for more up to date information.

Difference between revisions of "Lustre Project List"

From Obsolete Lustre Wiki
Jump to navigationJump to search
m (moved Lustre Features to Lustre Project List: Don't want to confuse this with existing features)
Line 3: Line 3:
 
Below is a list of Lustre features and projects that are just waiting for someone to start working on them.  They are listed roughly in order of increasing complexity, but this is highly dependent upon the coding skills of the developer and their familiarity with the Lustre code base.
 
Below is a list of Lustre features and projects that are just waiting for someone to start working on them.  They are listed roughly in order of increasing complexity, but this is highly dependent upon the coding skills of the developer and their familiarity with the Lustre code base.
  
{| border=1 cellpadding=0
+
{| border=2 cellpadding=0
 
|-
 
|-
 
!Feature
 
!Feature
Line 10: Line 10:
 
!Tracking Bug
 
!Tracking Bug
 
!Brief Description
 
!Brief Description
 +
|-
 +
|Improve testing Efficiency
 +
|1
 +
|shell, test
 +
|
 +
|<small>Improve the performance, efficiency, and coverage of acc-sm.  Improved test scheduling.  Dynamic cluster configuration.  Virtual machines for functional tests.</small>
 +
|-
 +
|Config save/edit/restore
 +
|3
 +
| MGS, llog, config
 +
|[https://bugzilla.lustre.org/show_bug.cgi?id=17094 17094]
 +
|<small>Need to be able to backup/edit/restore the client/MDS/OSS config llog files after a writeconf.  One reason is for config recovery if the config llog becomes corrupted.  Another reason is that all of the filesystem tunable parameters (including all of the OST pool definitions) are stored in the config llog and are lost if a writeconf is done.</small>
 
|-
 
|-
 
|mdd-survey tools for performance analysis
 
|mdd-survey tools for performance analysis
Line 24: Line 36:
 
</small>
 
</small>
 
|-
 
|-
 +
|Imperative recovery
 +
|6
 +
|recovery, RPC
 +
|[https://bugzilla.lustre.org/show_bug.cgi?id=18767 18767]
 +
|<small>Reduce recovery time by having the server notify clients after recovery has completed instead of waiting for the client to timeout the RPC before it begins recovery.</small>
 
|}
 
|}

Revision as of 15:25, 5 September 2010

List of Lustre Features and Projects

Below is a list of Lustre features and projects that are just waiting for someone to start working on them. They are listed roughly in order of increasing complexity, but this is highly dependent upon the coding skills of the developer and their familiarity with the Lustre code base.

Feature Complexity Required skills Tracking Bug Brief Description
Improve testing Efficiency 1 shell, test Improve the performance, efficiency, and coverage of acc-sm. Improved test scheduling. Dynamic cluster configuration. Virtual machines for functional tests.
Config save/edit/restore 3 MGS, llog, config 17094 Need to be able to backup/edit/restore the client/MDS/OSS config llog files after a writeconf. One reason is for config recovery if the config llog becomes corrupted. Another reason is that all of the filesystem tunable parameters (including all of the OST pool definitions) are stored in the config llog and are lost if a writeconf is done.
mdd-survey tools for performance analysis 3 obdfilter-survey, mdd, benchmarking 21658 Add a low-level metadata unit test to allow measuring performance of the metadata stack without having connected clients, similar and/or integrated to the obdfilter survey (echo client, echo server)
32TB ldiskfs filesystems 5 ldiskfs, obdfilter 20063 Single OST sizes larger than 16TB. This is largely supported in newer ext4 filesystems (e.g. RHEL5.4, RHEL6), but thorough testing and some bug fixing work may be needed in obdfilter (1.8, 2.0) or OFD (2.x), and other work may be needed in client (all versions).

Imperative recovery 6 recovery, RPC 18767 Reduce recovery time by having the server notify clients after recovery has completed instead of waiting for the client to timeout the RPC before it begins recovery.