Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <32826726.3931273693505828.JavaMail.jira@thor>
Date: Wed, 12 May 2010 15:45:05 -0400 (EDT)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5670) Hadoop configurations should be
 read from a distributed system
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866707#action_12866707 ] 

Allen Wittenauer commented on HADOOP-5670:
------------------------------------------

+1 on abstraction

> LDAP is a protocol, not a storage system. Which implementation did you have in mind? 

LDAP is a well understood, well documented, and RFC standardized protocol. The implementation on the back-end is almost completely irrelevant as long as we follow the RFCs (and few offer extensions anyway).  The only place where the back-end matters is in the raw schema definition file, as some implementations expect slightly different text formatting.  Converting from, say, OpenLDAP's format to Sun/Fedora ... is trivial and all LDAP admins are used to it. :)

> Kerberos is normally backended by LDAP, so a good point of users will have an ldap server at their disposal.

This is a claim I'm not sure I'd make.  By far, the biggest LDAP installations also happen to be Kerberos installations (thanks Active Directory!), but I suspect many places treat these as separate systems (MIT KDCs just got LDAP backend support in the past few years).

In other news, I wrote up some random notes (implementation ideas?  requirements? lots of stuff buried in there) at:

http://wiki.apache.org/hadoop/IdeasOnLdapConfiguration

It also includes a very quick 'n dirty LDAP tutorial to help those unfamiliar with how useful the object search aspect is to making the configuration stuff full featured and more useful than just storing raw XML (which is what I suspect the ZK crowd is thinking).

> Hadoop configurations should be read from a distributed system
> --------------------------------------------------------------
>
>                 Key: HADOOP-5670
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5670
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: conf
>            Reporter: Allen Wittenauer
>
> Rather than distributing the hadoop configuration files to every data node, compute node, etc, Hadoop should be able to read configuration information (dynamically!) from LDAP, ZooKeeper, whatever.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.