[985] in athena10
Re: nss: hesiod -> ldap for groups?
daemon@ATHENA.MIT.EDU (Jonathan Reed)
Mon Jan 26 12:39:44 2009
Cc: athena10@mit.edu
Message-Id: <4F554A86-721E-4A8C-8EDE-ADB9F0B14AC4@mit.edu>
From: Jonathan Reed <jdreed@MIT.EDU>
To: Evan Broder <broder@mit.edu>
In-Reply-To: <49799A6B.4000801@mit.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 26 Jan 2009 12:38:26 -0500
> I think we should pursue updating ldap.mit.edu to give us the
> information we want, but I'm not sure what the political playing field
> looks like there. IS&T people: is it likely that we can get
> ldap.mit.edu
> fixed up for this? Or should we suck it up and deal with and
> continue to
> try to fix Hesiod groups?
Based on several hallway conversations, I will make the assertion that
NFS groups should be considered legacy in the Athena 10 world, and
that we should move forward with getting group information from
somewhere like AD.
I don't think implementation of this should be a blocker to going live
with the Early release, however I think it should block on:
- technical feasibility
- agreement from AD maintainers that implementation can occur before
Summer cluster deployment.
I will attempt to capture this in Jira, but I'm in WIN.MIT.EDU
training for most of the day.
-Jon
