[cdwg] Lustre 2.5 Development Planning

[Christopher J. Morrone]

Ok, I guess I'll start things off.  Here is my first pass at things I 
would like to see done by 2.5:

LU-793 - Reconnections should not be refused when there is a request in 
progress from this client.
LU-2498 - set block device IO scheduler to "deadline"
LU-1199 - lustre build system overhaul
LU-2182 - New llapi_layout API implementation
LU-3338 - IOC_MDC_GETFILESTRIPE can abuse vmalloc()
LU-2158 - remove lvfs and fsfilt code
LU-2161 - Remove last traces of obdfilter
LU-2096 - name ofd device type "ofd" instead of "obdfilter"
LU-911 - OFD Supporting Proc Updates
LU-2613 - opening and closing file can generate 'unrelaimable slab' space
LU-2259 - e2fsprogs: rename liblustreapi.h with lustreapi.h
LU-2600 - lustre metadata performance is very slow on zfs
LU-2476 - poor OST file creation rate performance with zfs backend
LU-2139 - track unstable pages on client
LU-1784 - freeing cached clean pages is slow
LU-744 - Single client's performance degradation on 2.1
LU-576 - Incorrect build dependencies listed for libcfsutil.a
LU-2800 - build: clean out old autoconf options

Chris

On 05/22/2013 10:41 AM, Christopher J. Morrone wrote:
> Hi folks,
>
> Please send us your list of planned development items for Lustre 2.5! In
> two weeks at the next CDWG meeting we will be looking at the list of
> proposed work and making our first, best attempt at pare it down to a
> reasonable set of work for Lustre 2.5.
>
> If you have a new feature that you believe will be ready to land with in
> the three month feature-landing window of Lustre 2.5, NOW is the time to
> tell us!
>
> If you have pet bugs that are stuck on the back burner and need to be
> made a development priority for Lustre 2.5, NOW is the time to tell us!
>
> Your input is crucial if we are to properly scope the amount of change
> that we will introduce for Lustre 2.5, and properly scoping the work is
> a requirement if we are to produce a solid, on-time software release.
>
> So don't delay!  Send us your list of desired Lustre 2.5 development
> items to this mailing list as soon as possible.
>
> Then, join us in the next CDWG call on June 5th to help us choose the
> subset of work that we believe is achievable* for Lustre 2.5.
>
> Chris
>
> * Not that this list will only be our best attempt at scoping what is
> reasonable, and is by no means a guarantee that any particular item will
> appear in Lustre 2.5.
> .
>