[Lustre-devel] [wc-discuss] Lustre 2.3 release
bergwolf at gmail.com
Fri Feb 17 21:00:47 PST 2012
On Sat, Feb 18, 2012 at 5:48 AM, Nathan Rutman
<Nathan_Rutman at xyratex.com> wrote:
> On Feb 15, 2012, at 6:15 PM, <tao.peng at emc.com> <tao.peng at emc.com> wrote:
>> Hi Peter,
>> Thanks for bringing it up. As the target date for 2.3 is September 2012, I'd like to add some EMC tasks (not necessary features though) that we hope to land in 2.3 release cycle. Please consider including them in your planning.
>> 1. remove obsolete configure macros that are there to support old kernels (older than 2.6.18-latest)
>> 2. Lustre client dcache clean up
>> 3. separate server connection handling from ptlrpc layer
> Can you explain a little more about this one?
Our purpose is to clean up Lustre client to some extent that we can
push it into upstream Linux kernel. And per discussion with Andreas,
we want to split some server code dependency from client so that we
don't need dive deep into server code.
>> 4. client kernel API adjustment to latest upstream kernel
>> 5. client module build process change to adapt to vanilla kernel
>>> -----Original Message-----
>>> From: Peter Jones [mailto:pjones at whamcloud.com]
>>> Sent: Tuesday, February 07, 2012 6:03 AM
>>> To: cdwg at lists.opensfs.org; wc-discuss at whamcloud.com
>>> Subject: [wc-discuss] Lustre 2.3 release
>>> Hi there
>>> Although we are still very busy with Lustre 2.2, we have started
>>> planning for the content of Lustre 2.3 release. Landings for 2.3 will
>>> start as soon as Lustre 2.2 has been branched from master.
>>> Lustre 2.3 is targeted for release in September 2012 and, as such, any
>>> features to be included will need to be landed to master by the end of
>>> June at the latest in order to allow adequate time for stabilization
>>> ahead of the release. If features only become ready for landing at the
>>> end of June there may not be sufficient time to land them all, so
>>> features that are available sooner are more likely to be tested,
>>> inspected, and landed before the feature freeze.
>>> If anyone is working on features that could be candidates to include in
>>> this release then please let me know so that we can consider them in our
>>> Features that were initially targeted for 2.2 but were not ready in time
>>> are already on our list -
>>> Peter Jones
>>> Whamcloud, Inc.
> Lustre-devel mailing list
> Lustre-devel at lists.lustre.org
More information about the lustre-devel