[nfsv4] [FedFS] Meeting Minutes, 2/11/2010
James Lentini <jlentini@netapp.com> Thu, 11 February 2010 19:43 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 7D7E528C201 for <nfsv4@core3.amsl.com>; Thu, 11 Feb 2010 11:43:22 -0800 (PST)
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 gsf6G4LUb61N for <nfsv4@core3.amsl.com>; Thu, 11 Feb 2010 11:43:21 -0800 (PST)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by core3.amsl.com (Postfix) with ESMTP id 8522628C1FA for <nfsv4@ietf.org>; Thu, 11 Feb 2010 11:43:21 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.49,454,1262592000"; d="scan'208";a="315024546"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 11 Feb 2010 11:44:37 -0800
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 o1BJiaYO005010 for <nfsv4@ietf.org>; Thu, 11 Feb 2010 11:44:36 -0800 (PST)
Date: Thu, 11 Feb 2010 14:44:35 -0500
From: James Lentini <jlentini@netapp.com>
X-X-Sender: jlentini@jlentini-linux.nane.netapp.com
To: nfsv4@ietf.org
Message-ID: <alpine.LFD.2.00.1002111436460.30709@jlentini-linux.nane.netapp.com>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Subject: [nfsv4] [FedFS] Meeting Minutes, 2/11/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: Thu, 11 Feb 2010 19:43:22 -0000
FedFS Meeting Minutes, 2/11/2010 -------------------------------- Attendees --------- Craig Everhart (NetApp) Sorin Faibish (EMC) Paul LeMahieu (EMC) James Lentini (NetApp) Trond Myklebust (NetApp) Chris Stacey (EMC) Renu Tewari (IBM) Robert Thurlow (Sun) Minutes ------- + IETF Note Well Agreement This is a reminder that our discussions are governed by the IETF Note Well Agreement. See: http://www.ietf.org/NOTEWELL.html We will start each week's meeting with this announcement. + FedFS at Connectathon Rob Thurlow will be delivering two talks on Wednesday, February 24th: "FedFS State of the Union" at 2:00-3:00pm. Solaris "Referrals Implementation" at 4:00-4:30pm. Rob is planning to send out the FedFS presentation for review before Connectathon. Trond reported that the Linux FedFS implementation will be at Connectathon. Trond has updated it to the LDAP schema from: http://tools.ietf.org/html/draft-ietf-nfsv4-federated-fs-protocol-04 and is now using the latest version of the SNSDB code. Rob reported that the Solaris FedFS prototype from the Fall'09 bake-a-thon will be at Connectathon. Pavan has been working on updating to the -04 LDAP schema. Monday, February 22, looks like the earliest opportunity to start FedFS testing. + USENIX FAST'10 BOF The BOF room changed to Atherton. There will now be A/V available so we can put up some slides. The BOF will be from 7:30-8:30pm on Thursday, February 25. + NSDB Draft Review http://tools.ietf.org/html/draft-ietf-nfsv4-federated-fs-protocol-05 - Section 2.4.3 Generating A Referral from Fileset Locations - Section 4.2.1.2 fedfsNetAddr - other updates Craig and Rob thought 2.4.3 looked good. There were no other comments on this draft. + Admin Draft Review http://tools.ietf.org/html/draft-ietf-nfsv4-federated-fs-admin-04 - Section 5.3 FEDFS_LOOKUP_FSN - Section 5.4 FEDFS_SET_NSDB_PARAMS - Section 5.5 FEDFS_GET_NSDB_PARAMS - Section 5.6 FEDFS_GET_LIMITED_NSDB_PARAMS See thread http://www.ietf.org/mail-archive/web/nfsv4/current/msg07720.html - other updates The main discussion point on this draft was the name of the FEDFS_GET_LIMITED_NSDB_PARAMS procedure (see mailing list thread cited above). Trond suggests making the name more specific given that it only returns the security type. James explained his rational for choosing a generic name. The idea was that the procedure might return other results (the NCE?). He doesn't feel strongly about the name. If no other results are returned, he agreed that a more specific name would make sense. We discussed making the NCE an NSDB parameter. The benefit is that the NCE does not need to be included in every FEDFS_JUNCTION_CREATE request. If an NSDB has multiple NCEs (not currently allowed by definition in NSDB draft), how would this be expressed? When would this be used? Perhaps when multiple domains are hosted in the same LDAP directory? Need to think through this and see if it makes sense. The plan is to consider moving the NCE to be an NSDB parameter. If that change is made, then keep a generic name for FEDFS_GET_LIMITED_NSDB_PARAMS and include the NCE is the procedure results. If no change is made, rename FEDFS_GET_LIMITED_NSDB_PARAMS to be FEDFS_GET_NSDB_SECURITY_TYPE.
- [nfsv4] [FedFS] Meeting Minutes, 2/11/2010 James Lentini