Re: [nfsv4] [FedFS] Meeting Minutes, 9/16/2010
James Lentini <jlentini@netapp.com> Tue, 21 September 2010 14:41 UTC
Return-Path: <jlentini@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 DAC913A6A41 for <nfsv4@core3.amsl.com>; Tue, 21 Sep 2010 07:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.913
X-Spam-Level:
X-Spam-Status: No, score=-5.913 tagged_above=-999 required=5 tests=[AWL=0.686, 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 wAGs7djOJien for <nfsv4@core3.amsl.com>; Tue, 21 Sep 2010 07:41:15 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id DAB183A6A53 for <nfsv4@ietf.org>; Tue, 21 Sep 2010 07:41:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.56,400,1280732400"; d="scan'208";a="455388446"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 21 Sep 2010 07:41:25 -0700
Received: from jlentini-linux.hq.netapp.com (jlentini-linux.hq.netapp.com [10.97.16.21]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id o8LEfOji019431; Tue, 21 Sep 2010 07:41:25 -0700 (PDT)
Date: Tue, 21 Sep 2010 10:41:24 -0400
From: James Lentini <jlentini@netapp.com>
X-X-Sender: jlentini@jlentini-linux.nane.netapp.com
To: Robert Thurlow <Robert.Thurlow@oracle.com>
In-Reply-To: <4C97767A.4000506@oracle.com>
Message-ID: <alpine.LFD.2.00.1009211033340.21841@jlentini-linux.nane.netapp.com>
References: <alpine.LFD.2.00.1009161441300.21841@jlentini-linux.nane.netapp.com> <4C97767A.4000506@oracle.com>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Cc: nfsv4@ietf.org
Subject: Re: [nfsv4] [FedFS] Meeting Minutes, 9/16/2010
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: Tue, 21 Sep 2010 14:41:17 -0000
On Mon, 20 Sep 2010, Robert Thurlow wrote: > James Lentini wrote: > > FedFS Meeting Minutes, 9/16/2010 > > Hi folks, > > Apologies for missing the meeting, I had to take my wife to > the doctor. I am also going to miss the BAT, but we will > have the Solaris FedFS prototype code there for testing. > The bits we had last time are updated to draft-05 of the > admin spec and draft-09 of the NSDB spec. > > > + October Bake-a-thon Planning > > > > Chuck asked if anyone was planning to setup a DNS server with an > > NFS SRV record from draft-ietf-nfsv4-federated-fs-dns-srv-namespace? > > Nobody had plans to set one up, but we agreed that it would be > > interesting if there were NFS client implementations to test. > > > > To test the NFS SRV record, would a special root NFS server be > > necessary? Trond and Craig explained that a special server would not be > > necessary, assuming the NFS client is interpreting the DNS SRV record. The > > NFS server could be an ordinary fileserver or one that supports junctions. > > Either would work for testing the NFS SRV record. > > > > Trond suggested a competition: whoever gets their fileserver up first > > gets to be root. > > > > We'll coordinate with Sorin to configure a DNS server with an SRV > > record. > > I appear to have some modifications to the Solaris automounter > which work to do the DNS query and mount a FedFS namespace root. > They will be part of what we bring to the BAT. I can send along > a sample DNS server setup, as well. I think that would be great. > > James reported that he had begun updating the Admin draft. > > > - An error code (FEDFS_ERR_NSDB_REFERRAL) and text (5.3.1) was added > > for LDAP referrals. > > Should this not be FEDFS_ERR_LDAP_REFERRAL? The other LDAP related error values use a prefix of "FEDFS_ERR_NSDB_": FEDFS_ERR_NSDB_LDAP and FEDFS_ERR_NSDB_LDAP_VAL. FEDFS_ERR_NSDB_REFERRAL seemed to fit in that naming scheme. I think FEDFS_ERR_NSDB_LDAP_REFERRAL would also make sense. Does naming this error FEDFS_ERR_NSDB_LDAP_REFERRAL sound better or worse? -james
- [nfsv4] [FedFS] Meeting Minutes, 9/16/2010 James Lentini
- Re: [nfsv4] [FedFS] Meeting Minutes, 9/16/2010 sfaibish
- Re: [nfsv4] [FedFS] Meeting Minutes, 9/16/2010 James Lentini
- Re: [nfsv4] [FedFS] Meeting Minutes, 9/16/2010 sfaibish
- Re: [nfsv4] [FedFS] Meeting Minutes, 9/16/2010 sfaibish
- Re: [nfsv4] [FedFS] Meeting Minutes, 9/16/2010 Robert Thurlow
- Re: [nfsv4] [FedFS] Meeting Minutes, 9/16/2010 david.noveck
- Re: [nfsv4] [FedFS] Meeting Minutes, 9/16/2010 sfaibish
- Re: [nfsv4] [FedFS] Meeting Minutes, 9/16/2010 James Lentini
- Re: [nfsv4] [FedFS] Meeting Minutes, 9/16/2010 Robert Thurlow
- Re: [nfsv4] [FedFS] Meeting Minutes, 9/16/2010 James Lentini