I felt compelled to scrible something in regards to network directory services after seeing this comment:
I recently brainstormed with Corey on competing with active directory. I was debating speccing out an “Active Directory Killer” for UDS Mountain View. What do you guys think? Federico’s survey results prove that GNOME is being deployed in large numbers, is now not the time to architect an Active Directory killer? Of course I am at the mercy of the amount of finite resources that other people can contribute, so my idea is to at least be able to spec what admins want. If you want to help with this, mail me, so that we can show up to Mountain View prepared. The least we can do is spec something out in detail so that someday someone can make it happen.
posted on
whiprush’s blog.
Having been a network/sysadmin type since I was a wee lad, I have some strong feelings on directory services. As a long time Novell jockey, I have lots of experience with Novell’s NDS; which is/was one of the first commercial grade DSes out there. A short history lesson for those of you that might not have been doing this then: Circa 1995/1996, Novell has Netware 4 out - it includes NDS for the first time. This is a distinct change from the bindery system of old that Novell used since the early days. The bindery was 3 files that kept all the users, groups and rights matched up to provide what we though of as a network OS; authenticate users, the ability to serve files to the right people, and be pretty darn fexible. Only problem was that if you had two servers, you needed to have individual accounts on each server to use it. Kind of a pain with 2 or 3 servers, a nightmare if you had 100.
NDS changed all of that - now there was a central repository, synced across the servers, of users, groups, and now, for the first time, objects! It was nirvana, even with the growing pains. (Can you say Netware 4.0.2?)
Now, remember, Windows 95 was just out and NT4 was being released late summer. All that pretty GUI stuff still didn’t save you from the SAM and the non-hierarchy user management. Also, since disks/volumes were not objects in the SAM, file systems rights were a each server thing, using a totally different tool from what you created users with. How lame. How non enterprise. How 1995!
Netware Admin aka NWAdmin/Netadmin did all the good stuff via one app, for all your servers. How cool is that! Serious, this was a giant leap for those of us in the i386 server world. Like going to the moon.
Course, I think we all know where and how this story ends. Microsoft out marketed Novell, helped by all those great OEM deals and we sit where we are today.
This brings us to my thoughts on a directory service for the Linux shops out there. There is, of course, LDAP, which works, but it not close to being at the level of NDS (eDirectory) or AD for smoothness or ease of setup. You can always do Samba and AD, but that means, at this time, Windows Servers. I think the solution is existing: NDS. Novell is making itself a Linux company, so they need to make eDirectory work with all the distros out there - make a package: novell-edir-client.deb or .rpm or whatever that runs a admin through the steps to make it into the directory and gives all that neat background admin stuff up for admining. Figure you give away eDir and the packages and the Console1 type app and offer Zenworks as the stuff for cash. Also offer support on the directory, of course, but give it away for people to use. That would hurt AD. Bonus points if somebody makes NDS4NT work with Windows 2k3 and eDirectory. (DirXML was that product later in its life; no idea what the current status is there.)
Ah, that would be awesome. A real Directory Service and a real OS. That would be cool. Seriously, let us not try to start another directory service, from scratch and learn all the old mistakes, again. DSes are something that needs to work from the beginning, since all your stuff is in them, a major screw up and you might have to ‘rebuild’ your network. I’ve seen even mature DSes commit hara-kiri and cause the IT staff a 168 hour week. With the problem that F/OSS has in the corporate environment with legitimacy, having a OSS product eat itself in production would be bad.
So, to recap: Obi-wan Novell, you are our only hope before we screw ourselves, again.