Re: [nfsv4] Use of NFS clients as pNFS data servers...

Trond Myklebust <trond.myklebust@fys.uio.no> Mon, 06 July 2009 23:30 UTC

Return-Path: <trond.myklebust@fys.uio.no>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6852D3A6827 for <nfsv4@core3.amsl.com>; Mon, 6 Jul 2009 16:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hq2MA+JvNgw4 for <nfsv4@core3.amsl.com>; Mon, 6 Jul 2009 16:30:46 -0700 (PDT)
Received: from mail-out2.uio.no (mail-out2.uio.no [129.240.10.58]) by core3.amsl.com (Postfix) with ESMTP id 1FF3A28C341 for <nfsv4@ietf.org>; Mon, 6 Jul 2009 16:30:45 -0700 (PDT)
Received: from mail-mx4.uio.no ([129.240.10.45]) by mail-out2.uio.no with esmtp (Exim 4.69) (envelope-from <trond.myklebust@fys.uio.no>) id 1MNxdE-0001Vi-AA; Tue, 07 Jul 2009 01:29:56 +0200
Received: from c-68-40-207-222.hsd1.mi.comcast.net ([68.40.207.222] helo=[192.168.1.100]) by mail-mx4.uio.no with esmtpsa (SSLv3:CAMELLIA256-SHA:256) user trondmy (Exim 4.69) (envelope-from <trond.myklebust@fys.uio.no>) id 1MNxdC-0001B0-Rf; Tue, 07 Jul 2009 01:29:56 +0200
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: nfsv4@ietf.org
In-Reply-To: <1246922688.23966.18.camel@heimdal.trondhjem.org>
References: <1246922688.23966.18.camel@heimdal.trondhjem.org>
Content-Type: multipart/mixed; boundary="=-w8HY+QdBbAkdrUNDRzzK"
Date: Mon, 06 Jul 2009 19:29:50 -0400
Message-Id: <1246922990.23966.23.camel@heimdal.trondhjem.org>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1
X-UiO-Ratelimit-Test: rcpts/h 4 msgs/h 1 sum rcpts/h 6 sum msgs/h 2 total rcpts 788 max rcpts/h 27 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=_URIID_)
X-UiO-Scanned: D5854F1F7F1E5E3746C239A9748D0AC84B51698C
X-UiO-SPAM-Test: remote_host: 68.40.207.222 spam_score: -49 maxlevel 80 minaction 2 bait 0 mail/h: 1 total 23 max/h 5 blacklist 0 greylist 0 ratelimit 0
Subject: Re: [nfsv4] Use of NFS clients as pNFS data servers...
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nfsv4>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jul 2009 23:30:48 -0000

On Mon, 2009-07-06 at 19:24 -0400, Trond Myklebust wrote:
> Hi,
> 
> I've just posted a version 0 draft of a proposal for a minimal protocol
> extension to allow sharing of cached read-only data among NFS clients.
> The proposal intends to add a back-end protocol (a.k.a. 'control
> protocol') to allow certain trusted NFS clients to register as file
> layout type data servers, and to allow them to communicate with a
> metadata server in order to manage layouts.
> 
> Please see
> 
> http://www3.ietf.org/proceedings/staging/draft-myklebust-nfsv4-pnfs-backend-00.txt
> 
> Cheers
>   Trond

Urgh. The URL is failing. OK, see the following attachment then...

Cheers
  Trond