package: lwat
severity: wishlist
version: 0.17-4

----------  Forwarded Message  ----------

Subject: Merge LWAT and DHCP machine objects in LDAP?
Date: Tuesday 05 August 2008 20:24
From: Petter Reinholdtsen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]

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.

I suspect the DHCP server can be told to look for dhcpHost objects in
the entire LDAP three, and then we can extend LWAT to create and
maintain them.  But I am not sure, and someone need to test if this is
possible.

We could also write a script to create machine objects automatically
in LDAP based on the information collected by sitesummary.  This way,
new machines could automatically show up in LDAP and the admin only
need to assign the new machine to groups, instead of having to track
down IP and MAC addresses.

One issue to look at is if it is possible to allow completely
automatic update in LDAP using a sitesummary hook.  If that is
possible, new hosts could show up almost immediately after
installation.

Another thing to keep in mind is how machine objects will work if we
move the DNS server to fetch its configuration from LDAP too.

Any volunteers to work on this?  It should be solved before we release
the Lenny based Skolelinux version.

Happy hacking,
--
Petter Reinholdtsen

-------------------------------------------------------

----------  Forwarded Message  ----------

Subject: Re: Merge LWAT and DHCP machine objects in LDAP?
Date: Wednesday 06 August 2008 09:23
From: Finn-Arne Johansen <[EMAIL PROTECTED]>
To: Petter Reinholdtsen <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]

Petter Reinholdtsen skrev:
> 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.

There are now at least 3 machine objects that are stored in ldap:
 A machine that is a member of a net-group
 A machine that is member of the samba domain
 A machine that exists in DHCP
In a short distance I can see 2 or 3 more:
 DNS information for the host
 Reverse DNS information
 Squid access information (Or maybe that should be provided based on
netgroup)

I would like to be able to add a machine by entering all information on
into a single form.

For users, we use templates, and for the users there are 2 objects added
for each user added, the user object, and the personal group object. I'm
not sure if it's possible to add more than a couple of objects, due to
limitations in the schemas, but I've not tried. By now (if my memory is
correct) LWAT creates an object which combines netgroup with samba
domain-member (which is actually a user object). I've not tried to
combine DHCP-info with an existing machine object, but I think I tried
to combine a DHCP-object and a DNS object (to be used with pdns), and it
failed. But I'm still testing this.

Bug reports (preferably with patches) will be welcome at
http://bzz.no/lwat/trac/trac.cgi/newticket

--
Finn-Arne Johansen
[EMAIL PROTECTED] http://bzz.no/
EE2A71C6403A3D191FCDC043006F1215062E6642 062E6642

-------------------------------------------------------

----------  Forwarded Message  ----------

Subject: Re: Merge LWAT and DHCP machine objects in LDAP?
Date: Wednesday 06 August 2008 09:54
From: Petter Reinholdtsen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]

[Finn-Arne Johansen]

> I'm not sure if it's possible to add more than a couple of objects,
> due to limitations in the schemas, but I've not tried.

I tested to create a combined object using a script I wrote to
populate LDAP from sitesummary, and it failed with

  invalid structural object class chain (organizationalRole/dhcpHost)

I guess our schemas do not allow this. :(

I tried to create an object with these attributes:

    my $attr = [
                'cn'               => $hostname,
                'associatedDomain' => $dnsdomain,
                'ipHostNumber'     => $ipaddr,
                'macAddress'       => (@macaddr)[0],
                'dhcpHWAddress'    => (@hwaddr)[0],
                'dhcpStatements'   => "fixed-address $fqdn",
                'objectclass' => ['top',
                                  'organizationalRole',
                                  'domainRelatedObject',
                                  'ipHost',
                                  'dhcpHost',
                                  ],
                ];


Anyone got any idea how to solve this issue?

Happy hacking,
--
Petter Reinholdtsen

-------------------------------------------------------

Attachment: pgpVwT05jS6G1.pgp
Description: PGP signature

Reply via email to