Linux NFS development
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Sorin Faibish <sfaibish@emc.com>,
	"Peter Honeyman" <Honey@citi.umich.edu>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"nfsv4@ietf.org" <nfsv4@ietf.org>
Subject: Re: Discussion topics for the coming Bake-A-Thon
Date: Sun, 19 Sep 2010 16:12:32 +0200	[thread overview]
Message-ID: <4C961A50.5010000@panasas.com> (raw)
In-Reply-To: <op.vi7c6cmorwwil4@sfaibish1.corp.emc.com>

On 09/18/2010 02:33 AM, Sorin Faibish wrote:
> All,
> 
> I am trying to build an agenda for discussions during the coming  
> Bake-A-Thon
> at EMC October 4-8. I collected the last week several topics of interest  
> and
> I want to ask you all to add any other topics of interest so I can close  
> the
> agenda of the event. This is the list so far:
> 
> 1. Layoutcommit for file layout (Dave Noveck)
> 2. Server side copy - (James)
> 3. Sparse files and storage preferences (Dean, Sorin)
> 4. Secure NFS (David Quigly)
> 5. Extend cthon tests with callback operations tests (Peter Honeyman)

     And local/remote truncate torture tests.

> 6. Performance tests - tools and benchmarks (Peter Honeyman)

to 6 or 5. Cluster tests. .i.e use of more then one client in concertration
to confuse and crash a server.

> 7. Utils and fedora rpm (Sorin, SteveD)
> 8. pNFS with IPv6 (Sorin)
> 9. Linux FedFS imlementation (Chuck)
> 
> I will allocate 30min for each topic and group them in 2 hours sessions
> mostly in the early PM after lunch.
> 
> Please feel free to add any additional topics and thank you for your  
> patience.
> 
> /Sorin
> 


Thanks
Boaz

  reply	other threads:[~2010-09-19 14:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-18  0:33 Discussion topics for the coming Bake-A-Thon Sorin Faibish
2010-09-19 14:12 ` Boaz Harrosh [this message]
2010-09-19 14:49   ` [nfsv4] " Sorin Faibish
2010-09-19 14:59     ` Boaz Harrosh
2010-09-20 16:19     ` [nfsv4] " Thomas Haynes
2010-09-20 19:47       ` david.noveck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C961A50.5010000@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=Honey@citi.umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@ietf.org \
    --cc=sfaibish@emc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox