[cdwg] [wc-discuss] Lustre 2.3 release

[Peter Jones]

Kevin

I have added this column to the table.

As I explained on the call, my concern with having such a column was 
that it might cause confusion in the community if the targeted release 
supplied does not prove to be realistic.

In the past we ran into issues where people had relied on timelines in 
aggressive roadmaps and planned around them, and then were left in 
trouble when the features were not delivered according to the schedule. 
That is why we have consciously published conservative roadmaps with the 
intention of over-delivering.

However, I can see this option being of interest to the community so I 
am ok with giving this a try.

Hopefully having all the design documents, test plan being in the open 
in JIRA and the code uploaded into gerrit will enable interested parties 
to see for themselves how things are progressing and perhaps it will 
prove useful to spark a dialogue if there appears to be a divergence in 
expectations.

Regards

Peter

On 12-02-15 12:53 PM, Kevin Canady wrote:
> Peter
> This is great, many thanks, it's a good demonstration how much is being
> done to move Lustre forward.  If it would not further complicate, it would
> be helpful to have some reference to the targeted release of the
> features.Can we add a column to the list?  The obvious "right to change"
> would be in place.  The reference is only to help set expectations within
> the community.
>
> Sound reasonable?
>
> Thanks again,
> Kevin
>
> On 2/15/12 10:55 AM, "Peter Jones"<pjones at whamcloud.com>  wrote:
>
>> Nathan
>>
>> I have created placeholders for these items on the wiki. It would be
>> great if you could elaborate as to the nature of these features -
>> preferably creating a JIRA ticket with design docs etc attached. I am
>> assuming for now that the NRS items will be covered by the existing NRS
>> ticket (LU-398) but please let me know if that is not the case.
>>
>> Thanks
>>
>> Peter
>>
>> On 12-02-15 10:10 AM, Nathan Rutman wrote:
>>> Re: cdwg concall this morning,
>>> Peter sent out a link to the community's ongoing development wiki page
>>> last week.
>>>
>>> I'd like to add some Xyratex plans that I posted to TWG in early Jan:
>>>
>>> 3/12 CRC-32c SW (crypto-api version of CRC-32c so that it is no longer
>>> cpu-specific.)
>>> 3/12 CRC-32 HW (add HW acceleration to crypto-api version of CRC-32,
>>> and use it.)
>>> 4/12 4MB IO
>>> 4/12 NRS noop (null policy)
>>> 5/12 NRS obrr (object-based round-robin policy)
>>> 7/12 End-to-End Data Integrity with T10
>>>
>>>
>>> On Feb 6, 2012, at 2:03 PM, Peter Jones wrote:
>>>
>>>> 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 planning.
>>>>
>>>> Features that were initially targeted for 2.2 but were not ready in
>>>> time are already on our list -
>>>> http://wiki.whamcloud.com/display/PUB/Lustre+Community+Development+in+Pr
>>>> ogress
>>>>
>>>> Thanks
>>>>
>>>> Peter
>>>>
>>>> -- 
>>>> Peter Jones
>>>> Whamcloud, Inc.
>>>> www.whamcloud.com
>>>>
>> -- 
>> Peter Jones
>> Whamcloud, Inc.
>> www.whamcloud.com
>>
>> _______________________________________________
>> cdwg mailing list
>> cdwg at lists.opensfs.org
>> http://lists.opensfs.org/listinfo.cgi/cdwg-opensfs.org
>
>

-- 
Peter Jones
Whamcloud, Inc.
www.whamcloud.com