OK - I actually like and enjoy LDAP, but do not allow that to cloud your judgment. LDAP took much more of my time and effort to learn than Bind and/or DNS. And I recall sitting in front of DNS chapters wondering why we needed another language to do something as easy as mapping a friendly name to an IP address. This jargon stuff has value though such as constraing insomnia.
So, if you need some sleep and don't care about writers who use phrases like "much more", then we can move along and discuss the notion of an objectClass. Are we having fun yet?
The entries in an LDAP directory, like the entries in a phone book or contact list require objectClass attributes which need at least one value. That's just common sense right?
Think of an objectClass value as a template for the information you wish to store in an entry or to make the jargon complete in the name space.
We haven't touched on distinguished names and relative distinguished names but pretend like you know what they mean, please. In the example below, think of an "organizational unit" as the top of a hierarchical file system with limbs below it.
The top of directory for our purpose is ou=computers,dc=centralsoft,dc=org. So, if you wanted to find a list of computers in centralsoft.org, you would have this area of the directory called computers. Computers would appear in your LDAP browser in plain English as simply "Computers" and below that one or more computers.
In LDAP parlance setting up the area of the directory for computers would look like this:
description: Container for all computers existing within the centralsoft.org domain
The objectClass attribute we used in this example was "pc". The only pc that the directory contains at the moment is "wkst01". You could just as easily used "srv01" for "server01". That's not the point though.
Technically speaking, of course, RFCs define many attributes we find in LDAP schemas. For example RFC 2256 defines the attribute for telephoneNumber, which intuitively makes total sense to the average user of a contact list (sic).
We just touched the surface of the objectClass discussion. Don't worry if it does not make much sense at this point. Just know that in the language or jargon of LDAP, you'll have to get it about objectClass attributes or you won't have much to do with constructing LDAP directories.
|Speed Up Your Web Site with Varnish||Jun 19, 2013|
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
- Containers—Not Virtual Machines—Are the Future Cloud
- Non-Linux FOSS: libnotify, OS X Style
- Linux Systems Administrator
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Validate an E-Mail Address with PHP, the Right Way
- Technical Support Rep
- Senior Perl Developer
- UX Designer
- Introduction to MapReduce with Hadoop on Linux
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?