[Twg] TWG meeting 5/31/2012: last chance for input on recommendations
John Carrier
carrier at cray.com
Wed May 30 04:20:13 UTC 2012
For everyone's benefit, Nathan added the following text to the recommendation:
[NZR] Also, an LNET channel bonding requirement was ranked highly by
OpenSFS promoters; however this feature may address availability (if
graceful degradation facilities are included) as well as improved
single-client performance, and so may be considered under those categories.
Andreas also pointed out that "Dynamic LNET configuration" was also rated highly. If taken as a whole, we have three LNET features that people have rated highly. Instead of cramming LNET into Availability, let's keep them separate and make four recommendations to the board: availability, performance, storage management and LNET.
Remember that we are making a recommendation to the Board. They will decide our budget and tell us the priority for the RFPs that we prepare.
--jc
-----Original Message-----
From: twg-bounces at lists.opensfs.org [mailto:twg-bounces at lists.opensfs.org] On Behalf Of Nathan Rutman
Sent: Tuesday, May 29, 2012 4:59 PM
To: twg at lists.opensfs.org
Subject: Re: [Twg] TWG meeting 5/31/2012: last chance for input on recommendations
My apologies as well. I added a paragraph at the bottom of the Draft
http://goo.gl/7ncPT
we can discuss on Thurs.
Also for completeness we should talk about this:
1) Architecture/Developer documentation
Well documented internals of MDS, MGS, OSS, OST, OSD API, etc.
On May 29, 2012, at 3:01 PM, Andreas Dilger wrote:
> On 2012-05-29, at 1:45 PM, David Dillow wrote:
>> We discussed the recommendation to the board as well as testing and
>> release management topics during today's additional TWG meeting.
>> We will be incorporating the recommendation into the requirements
>> document as we did last year. We will note the community's interest in
>> improving the test infrastructure as maintaining patch lists for bug fix
>> releases, but will refer those topics to the CWG.
>>
>> We will be sending out updated documents later this evening.
>>
>> Due to the poor attendance for today's call, we have extended the
>> schedule slightly; we will be forwarding the recommendation to the board
>> shortly after Thursday's meeting. If you have wish to have your comments
>> heard, please make every effort to attend this week's TWG meeting.
>
> Apologies on missing the meeting. I didn't have anything in my calendar, and I guess I thought there would be a meeting invitation sent out. I'll see if I have any further feedback on the updated doc.
>
>> Thursday, 12:30pm ET/9:30 PT.
>> 715-726-4994 or toll-free 866-304-8294
>> Meeting ID and password: 72090
>>
>>
>> Current draft recommendation based on our review of the initial
>> spreadsheet (to be revised and redistributed this evening):
>> https://docs.google.com/document/d/1zwGkID8yENgdmmp9lsPgg9CInJXVbZoIfTjglKEB4RE/edit?pli=1
>>
>> Gathered requirements: http://goo.gl/63u9Q
>> The spreadsheet summarizing our priorities: http://goo.gl/Lqg7s
>>
>> Thanks,
>> John Carrier
>> Dave Dillow
>>
>> _______________________________________________
>> twg mailing list
>> twg at lists.opensfs.org
>> http://lists.opensfs.org/listinfo.cgi/twg-opensfs.org
>> _______________________________________________
>> twg mailing list
>> twg at lists.opensfs.org
>> http://lists.opensfs.org/listinfo.cgi/twg-opensfs.org
>
>
> Cheers, Andreas
> --
> Andreas Dilger Whamcloud, Inc.
> Principal Lustre Engineer http://www.whamcloud.com/
>
>
>
>
> _______________________________________________
> twg mailing list
> twg at lists.opensfs.org
> http://lists.opensfs.org/listinfo.cgi/twg-opensfs.org
_______________________________________________
twg mailing list
twg at lists.opensfs.org
http://lists.opensfs.org/listinfo.cgi/twg-opensfs.org
More information about the Twg
mailing list