From: Petter Reinholdtsen <pere@hungry.com>
Date: Wed, 23 Jun 2010 22:23:51 +0000 (+0000)
Subject: Ny oppføring.
X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/90c126ec61b6fdcf11a04b64d7128f6ce7361282?hp=c790f2ff4d7b27e3765965d422e5df6e24214d21

Ny oppføring.
---

diff --git a/blog/data/2010-06-24-ldap-schemas.txt b/blog/data/2010-06-24-ldap-schemas.txt
new file mode 100644
index 0000000000..6910170244
--- /dev/null
+++ b/blog/data/2010-06-24-ldap-schemas.txt
@@ -0,0 +1,43 @@
+Title: Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
+Tags: english, debian, debian-edu, nuug
+Date: 2010-06-24 00:25
+
+<p>A while back, I
+<a href="http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html">complained
+about the fact</a> that it is not possible with the provided schemas
+for storing DNS and DHCP information in LDAP to combine the two sets
+of information into one LDAP object representing a computer.</p>
+
+<p>In the mean time, I discovered that a simple fix would be to make
+the dhcpHost object class auxiliary, to allow it to be combined with
+the dNSDomain object class, and thus forming one object for one
+computer when storing both DHCP and DNS information in LDAP.</p>
+
+<p>If I understand this correctly, it is not safe to do this change
+without also changing the assigned number for the object class, and I
+do not know enough about LDAP schema design to do that properly for
+Debian Edu.</p>
+
+<p>Anyway, for future reference, this is how I believe we could change
+the
+<a href="http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00">DHCP
+schema</a> to solve at least part of the problem with the LDAP schemas
+available today from IETF.</p>
+
+<pre>
+--- dhcp.schema    (revision 65192)
++++ dhcp.schema    (working copy)
+@@ -376,7 +376,7 @@
+ objectclass ( 2.16.840.1.113719.1.203.6.6
+        NAME 'dhcpHost'
+        DESC 'This represents information about a particular client'
+-       SUP top
++       SUP top AUXILIARY
+        MUST cn
+        MAY  (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
+        X-NDS_CONTAINMENT ('dhcpService' 'dhcpSubnet' 'dhcpGroup') )
+</pre>
+
+<p>I very much welcome clues on how to do this properly for Debian
+Edu/Squeeze.  We provide the DHCP schema in our debian-edu-config
+package, and should thus be free to rewrite it as we see fit.</p>