[nfsv4] [FedFS] What LDAP directory implementation have folks been using for the NSDB thus far?

<stacey_chris@emc.com> Mon, 14 December 2009 22:10 UTC

Return-Path: <stacey_chris@emc.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 7AA073A6816 for <nfsv4@core3.amsl.com>; Mon, 14 Dec 2009 14:10:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.296
X-Spam-Level:
X-Spam-Status: No, score=-6.296 tagged_above=-999 required=5 tests=[AWL=0.302, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 owQ24MvQvQec for <nfsv4@core3.amsl.com>; Mon, 14 Dec 2009 14:10:37 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by core3.amsl.com (Postfix) with ESMTP id 1B0C93A63EC for <nfsv4@ietf.org>; Mon, 14 Dec 2009 14:10:34 -0800 (PST)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.3.2/Switch-3.1.7) with ESMTP id nBEMAKDX008320 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <nfsv4@ietf.org>; Mon, 14 Dec 2009 17:10:20 -0500
Received: from mailhub.lss.emc.com (numailhub.lss.emc.com [10.254.144.16]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor) for <nfsv4@ietf.org>; Mon, 14 Dec 2009 17:10:16 -0500
Received: from corpussmtp4.corp.emc.com (corpussmtp4.corp.emc.com [10.254.169.197]) by mailhub.lss.emc.com (Switch-3.4.2/Switch-3.3.2mp) with ESMTP id nBEMAFKQ017732 for <nfsv4@ietf.org>; Mon, 14 Dec 2009 17:10:16 -0500
Received: from CORPUSMX40A.corp.emc.com ([10.254.64.48]) by corpussmtp4.corp.emc.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 14 Dec 2009 17:10:15 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA7D0A.36CA1333"
Date: Mon, 14 Dec 2009 17:10:14 -0500
Message-ID: <0F3F903BA6B4A54984787888AF6EA5C4046728F7@CORPUSMX40A.corp.emc.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [FedFS] What LDAP directory implementation have folks been using for the NSDB thus far?
thread-index: Acp9CjYPsmOg9719TOWoxeXpeKgmPg==
From: stacey_chris@emc.com
To: nfsv4@ietf.org
X-OriginalArrivalTime: 14 Dec 2009 22:10:15.0730 (UTC) FILETIME=[36E06120:01CA7D0A]
X-EMM-EM: Active
Subject: [nfsv4] [FedFS] What LDAP directory implementation have folks been using for the NSDB thus far?
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, 14 Dec 2009 22:10:41 -0000

Hi,

 

Just curious - what LDAP directory implementation you been using for the
NSDB in a FedFS setup thus far?   Any issues?   Good points?

 

Thanks,
Chris

-- 
Chris Stacey - Senior Technologist, Celerra Unified Storage Engineering,
EMC Corporation (New Zealand).  Phone: +64 21 225 3747