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

Trond Myklebust <Trond.Myklebust@netapp.com> Mon, 06 July 2009 23:25 UTC

Return-Path: <Trond.Myklebust@netapp.com>
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 CDEBE28C410 for <nfsv4@core3.amsl.com>; Mon, 6 Jul 2009 16:25:34 -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 Cbf7xxrl9VwA for <nfsv4@core3.amsl.com>; Mon, 6 Jul 2009 16:25:33 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id CAF5C28C36E for <nfsv4@ietf.org>; Mon, 6 Jul 2009 16:25:33 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,359,1243839600"; d="scan'208";a="201260939"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 06 Jul 2009 16:25:27 -0700
Received: from svlrsexc1-prd.hq.netapp.com (svlrsexc1-prd.hq.netapp.com [10.57.115.30]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id n66NPRLo021323; Mon, 6 Jul 2009 16:25:27 -0700 (PDT)
Received: from SACMVEXC2-PRD.hq.netapp.com ([10.99.115.18]) by svlrsexc1-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 6 Jul 2009 16:25:26 -0700
Received: from 10.58.48.240 ([10.58.48.240]) by SACMVEXC2-PRD.hq.netapp.com ([10.99.115.16]) with Microsoft Exchange Server HTTP-DAV ; Mon, 6 Jul 2009 23:24:49 +0000
Received: from heimdal.trondhjem.org by SACMVEXC2-PRD.hq.netapp.com; 06 Jul 2009 19:24:49 -0400
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: nfsv4@ietf.org
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: NetApp
Date: Mon, 06 Jul 2009 19:24:48 -0400
Message-Id: <1246922688.23966.18.camel@heimdal.trondhjem.org>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1
X-OriginalArrivalTime: 06 Jul 2009 23:25:26.0874 (UTC) FILETIME=[0B3893A0:01C9FE91]
Subject: [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:25:34 -0000

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

-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com