On Tue, Aug 05, 2008 at 08:24:20PM +0200, Petter Reinholdtsen wrote: > > With the introduction of DHCP configuration in LDAP, we also > introduced a new kind of machine object in LDAP. The way our LDAP > currently is structured these machine objects are not seen by LWAT, > and machine objects created by LWAT are not seen by the DHCP server. > Someone should look into merging the two.
Here are two example objects, the first one from the DHCP configuration, the second created by LWAT. dn: cn=ltspserver00,cn=group1,cn=INTERNAL,cn=DHCP Config,dc=skole,dc=skolelinu x,dc=no cn: ltspserver00 objectClass: top objectClass: dhcpHost dhcpHWAddress: ethernet 00:00:00:00:00:00 dhcpStatements: fixed-address ltspserver00 structuralObjectClass: dhcpHost entryUUID: 5167ffbc-f79d-102c-9856-3f0d4c5d7236 creatorsName: cn=admin,ou=People,dc=skole,dc=skolelinux,dc=no createTimestamp: 20080806004949Z entryCSN: 20080806004949.796386Z#000000#000#000000 modifiersName: cn=admin,ou=People,dc=skole,dc=skolelinux,dc=no modifyTimestamp: 20080806004949Z dn: cn=tjener,ou=Machines,ou=People,dc=skole,dc=skolelinux,dc=no objectClass: top objectClass: organizationalRole objectClass: domainRelatedObject objectClass: ipHost cn: tjener associatedDomain: intern ipHostNumber: 10.0.2.2 structuralObjectClass: organizationalRole entryUUID: 835ca4c8-f7cf-102c-957e-a90a6065200e creatorsName: cn=admin,ou=People,dc=skole,dc=skolelinux,dc=no createTimestamp: 20080806064908Z entryCSN: 20080806064908.444431Z#000000#000#000000 modifiersName: cn=admin,ou=People,dc=skole,dc=skolelinux,dc=no modifyTimestamp: 20080806064908Z I suspect it would be a good idea to tell both the DHCP server and LWAT to look for hosts under the top of the tree (dc=skole,dc=skolelinux,dc=no), instead of only under a spesific subtree, to avoid having to decide where to store machines. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
