Return-Path: From: Thomas Haynes In-Reply-To: Date: Mon, 20 Sep 2010 11:19:30 -0500 Message-Id: References: <4C961A50.5010000@panasas.com> To: Sorin Faibish Cc: "linux-nfs@vger.kernel.org" , Peter Honeyman , "nfsv4@ietf.org" , Boaz Harrosh Subject: Re: [nfsv4] Discussion topics for the coming Bake-A-Thon List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0863728073==" Sender: nfsv4-bounces@ietf.org Errors-To: nfsv4-bounces@ietf.org MIME-Version: 1.0 List-ID: --===============0863728073== Content-Type: multipart/alternative; boundary=Apple-Mail-13--397790676 --Apple-Mail-13--397790676 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii =20 On Sep 19, 2010, at 9:49 AM, Sorin Faibish wrote: > On Sun, 19 Sep 2010 10:12:32 -0400, Boaz Harrosh = wrote: >=20 >> On 09/18/2010 02:33 AM, Sorin Faibish wrote: >>>=20 >>> 5. Extend cthon tests with callback operations tests (Peter = Honeyman) >>=20 >> And local/remote truncate torture tests. > Sure. Do we need a separate discussion or only this? >=20 >>=20 >>> 6. Performance tests - tools and benchmarks (Peter Honeyman) >>=20 >> to 6 or 5. Cluster tests. .i.e use of more then one client in = concertration >> to confuse and crash a server. > This aside from cthon, just for performance qaulification for the git. > Same do we need an additional spot or this is enough (30 min). >=20 > I will update the agenda with your comments and I assume you will be > part of the discussion, even drive it. >=20 > /Sorin >=20 One subject I would like to see us address as a community is where we go with respect to our general testing strategy. We have had discussions = the last several years at the Connectathons about the ability to contribute = to the cthon test suites and the legal status of the code. Basically, because of the lack of understanding of the licensing, I = believe companies are not contributing changes back into the shared code base. We can talk about what it would take to get the license straightened = out, but it might be more expedient to acknowledge that the cthon test suite = is a low bar and drive the creation of a new test suite. --Apple-Mail-13--397790676 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii  


<= div>One subject I would like to see us address as a community is where we g= o
with respect to our general testing strategy. We have had discu= ssions the
last several years at the Connectathons about the abil= ity to contribute to the
cthon test suites and the legal status o= f the code.

Basically, because of the lack of unde= rstanding of the licensing, I believe
companies are not contribut= ing changes back into the shared code base.

We can= talk about what it would take to get the license straightened out,
but it might be more expedient to acknowledge that the cthon test suite = is
a low bar and drive the creation of a new test suite.
= --Apple-Mail-13--397790676-- --===============0863728073== Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ nfsv4 mailing list nfsv4@ietf.org https://www.ietf.org/mailman/listinfo/nfsv4 --===============0863728073==--