Re: Problem with sitesummary2ldapdhcp
On Sat, Feb 11, 2012 at 11:25:42AM +0100, Giorgio Pioda wrote: > > > So if you only want to assign netgroups and DNS/DHCP, the netdevices > > seem to be the best fit. > > I've tried several times, but got no connection. What I'm missing? > I put MAC and IP enable DHCp and DNS, and add workstation in NIS Netgroup. Check the LDAP data base using ldapvi. There might be objects from a previous configuration (same MAC) causing the failure. Delete them and things will hopefully work. Wolfgang signature.asc Description: Digital signature
Re: Problem with sitesummary2ldapdhcp
Hi Petter, On Fr 10 Feb 2012 22:20:57 CET Petter Reinholdtsen wrote: I hope someone knowing GOsa² more can comment on the correct way to create system objects for computers. I created the same type of objects that tjener already got, and assume it is the correct thing to do for Linux hosts. The first list of LDAP objects was incomplete. The one shown here first was missing... dn: cn=workstations-01,ou=netdevices,ou=systems,dc=skole,dc=skolelinux,dc=no cn: workstations-01 ipHostNumber: 10.0.2.51 macAddress: aa:bb:cc:dd:ee:ff objectClass: top objectClass: device objectClass: ipHost objectClass: ieee802Device dn: cn=workstations-01,cn=10.0.0.0,cn=intern,cn=dhcp,cn=tjener,ou=servers,ou=systems,dc=skole,dc=skolelinux,dc=no dhcpOption: host-name workstations-01 dhcpStatements: fixed-address 10.0.2.51 cn: workstations-01 objectClass: top objectClass: dhcpHost dhcpHWAddress: ethernet aa:bb:cc:dd:ee:ff dn: relativeDomainName=workstations-01,zoneName=intern,cn=tjener,ou=servers,ou=systems,dc=skole,dc=skolelinux,dc=no objectClass: top objectClass: dNSZone dNSClass: IN zoneName: intern relativeDomainName: workstations-01 dn: relativeDomainName=workstations-01,relativeDomainName=workstations-01,zoneName=intern,cn=tjener,ou=servers,ou=systems,dc=skole,dc=skolelinux,dc=no objectClass: top objectClass: dNSZone dNSClass: IN zoneName: intern relativeDomainName: workstations-01 aRecord: 10.0.2.51 dn: relativeDomainName=51.2.0,relativeDomainName=workstations-01,zoneName=intern,cn=tjener,ou=servers,ou=systems,dc=skole,dc=skolelinux,dc=no objectClass: top objectClass: dNSZone dNSClass: IN zoneName: 10.in-addr.arpa. relativeDomainName: 51.2.0 pTRRecord: workstations-01.intern. Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpR8oZXUh7wx.pgp Description: Digitale PGP-Unterschrift
Re: Problem with sitesummary2ldapdhcp
Hi Petter, hi Wolfgang, On Fr 10 Feb 2012 22:20:57 CET Petter Reinholdtsen wrote: [Wolfgang Schweer] Additionally I noticed that the hosts were put into LDAP as »servers«, I'd expect »netdevices«. Why? I always create servers, also manually. Because they are for machines that in time can be managed by GOsa², while netdevices can not be managed. I rather recommend using a GOsa² object ,,server'' for real servers only, the GOsa² netdevice object, however, for everything else (i.e. skole desktops, diskless workstations, network printers, etc.). There is a gosa-plugin-goto that provides extended workstation support in GOsa² but the squeeze version is not usable. We have to wait for wheezy (gosa-2.7.x) with that. gosa-plugin-goto also offers printers and FAI integration and many more features. This workaround puts removeable objects into LDAP (like those created manually using GOsa²); only drawback is that one more click is needed in GOsa² (to enable DHCP). I hope someone knowing GOsa² more can comment on the correct way to create system objects for computers. I created the same type of objects that tjener already got, and assume it is the correct thing to do for Linux hosts. The GOsa² way of creating a netdevice (,,workstation-01'' in this case) looks like this: dn: cn=workstations-01,cn=10.0.0.0,cn=intern,cn=dhcp,cn=tjener,ou=servers,ou=systems,dc=skole,dc=skolelinux,dc=no dhcpOption: host-name workstations-01 dhcpStatements: fixed-address 10.0.2.51 cn: workstations-01 objectClass: top objectClass: dhcpHost dhcpHWAddress: ethernet aa:bb:cc:dd:ee:ff 180 relativeDomainName=workstations-01,zoneName=intern,cn=tjener,ou=servers,ou=systems,dc=skole,dc=skolelinux,dc=no objectClass: top objectClass: dNSZone dNSClass: IN zoneName: intern relativeDomainName: workstations-01 181 relativeDomainName=workstations-01,relativeDomainName=workstations-01,zoneName=intern,cn=tjener,ou=servers,ou=systems,dc=skole,dc=skolelinux,dc=no objectClass: top objectClass: dNSZone dNSClass: IN zoneName: intern relativeDomainName: workstations-01 aRecord: 10.0.2.51 182 relativeDomainName=51.2.0,relativeDomainName=workstations-01,zoneName=intern,cn=tjener,ou=servers,ou=systems,dc=skole,dc=skolelinux,dc=no objectClass: top objectClass: dNSZone dNSClass: IN zoneName: 10.in-addr.arpa. relativeDomainName: 51.2.0 pTRRecord: workstations-01.intern. I assume netdevice is for routers and switches, not for Linux hosts. If this is wrong, please tell me and we can easiliy change this. Told herewith. It is not wrong but I would rather recommend the netdevice. Happy hacking Petter Reinholdtsen Best, Mike -- DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419 GnuPG Key ID 0xB588399B mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpUuuUfK9mB9.pgp Description: Digitale PGP-Unterschrift
Re: Problem with sitesummary2ldapdhcp
[Andreas B. Mundt] > So if you only want to assign netgroups and DNS/DHCP, the netdevices > seem to be the best fit. OK. I've rewritten sitesummary2ldapdhcp in svn to do this now. This way we can remove the objects using GOsa. :) -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-edu-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2fl7gzt7ahr@diskless.uio.no
Re: Problem with sitesummary2ldapdhcp
Hi > So if you only want to assign netgroups and DNS/DHCP, the netdevices > seem to be the best fit. I've tried several times, but got no connection. What I'm missing? I put MAC and IP enable DHCp and DNS, and add workstation in NIS Netgroup. Regards Giorgio -- Sysadmin SPSE-Tenero Ufficio: +41 91 735 62 48 Cellulare: +41 79 629 20 63 -- To UNSUBSCRIBE, email to debian-edu-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120211102542.ga5...@ticino.com
Re: Problem with sitesummary2ldapdhcp
Hi all, On Fri, Feb 10, 2012 at 10:20:57PM +0100, Petter Reinholdtsen wrote: > > I assume netdevice is for routers and switches, not for Linux hosts. > If this is wrong, please tell me and we can easiliy change this. IIRC I used netdevice for all machines that do not serve any services to the network, so in a standard setup these are all machines except tjener (LTSP servers are independent and not managed by GOsa). Other profiles (Workstation etc.) are only available if you use certain plugins (gosa-fai ?), which we do not use. So if you only want to assign netgroups and DNS/DHCP, the netdevices seem to be the best fit. Regards, Andi -- To UNSUBSCRIBE, email to debian-edu-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120211081055.GA30050@fuzi
Re: Problem with sitesummary2ldapdhcp
On Fri, Feb 10, 2012 at 10:20:57PM +0100, Petter Reinholdtsen wrote: > > > Additionally I noticed that the hosts were put into LDAP as »servers«, > > I'd expect »netdevices«. > > Why? I always create servers, also manually. Because they are for > machines that in time can be managed by GOsa², while netdevices can > not be managed. There should be more choice than just servers and netdevices when creating a new system. Checked: It's possible to add netdevices to all NIS netgroups. Wolfgang signature.asc Description: Digital signature
Re: Problem with sitesummary2ldapdhcp
On Fri, Feb 10, 2012 at 10:20:57PM +0100, Petter Reinholdtsen wrote: > > > After an upgrade of the d-e-c package I added (diskless) hosts to > > the LDAP database using sitesummary2ldapdhcp - just for testing. All > > went well, but the database objects created were not removeable from > > within GOsa²; I had to use ldapvi to get rid of them. > > Does this also happen for the manually created servers? Yes, but that's sort of strange. > I hope someone knowing GOsa² more can comment on the correct way to > create system objects for computers. I created the same type of > objects that tjener already got, and assume it is the correct thing to > do for Linux hosts. > > I assume netdevice is for routers and switches, not for Linux hosts. Yes. > If this is wrong, please tell me and we can easiliy change this. https://oss.gonicus.de/demo/stable/ username: demo-admin pw: gosa They've got servers, workstations, winstations, terminals, netdevices. So I suppose, workstations would then be right. And: Icons there seem to show that even their servers are removeable - what makes sense to me. Wolfgang signature.asc Description: Digital signature
Re: Problem with sitesummary2ldapdhcp
[Wolfgang Schweer] > Hi, > > maybe due to an older install... Nope. What you describe is the currently intended behaviour. > After an upgrade of the d-e-c package I added (diskless) hosts to > the LDAP database using sitesummary2ldapdhcp - just for testing. All > went well, but the database objects created were not removeable from > within GOsa²; I had to use ldapvi to get rid of them. Does this also happen for the manually created servers? > Additionally I noticed that the hosts were put into LDAP as »servers«, > I'd expect »netdevices«. Why? I always create servers, also manually. Because they are for machines that in time can be managed by GOsa², while netdevices can not be managed. > This workaround puts removeable objects into LDAP (like those > created manually using GOsa²); only drawback is that one more click > is needed in GOsa² (to enable DHCP). I hope someone knowing GOsa² more can comment on the correct way to create system objects for computers. I created the same type of objects that tjener already got, and assume it is the correct thing to do for Linux hosts. I assume netdevice is for routers and switches, not for Linux hosts. If this is wrong, please tell me and we can easiliy change this. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-edu-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120210212057.gx31...@login2.uio.no
