Corey Osman wrote:
Hi,
I have a large datacenter about 2000 systems or more so my dhcpd.conf
is very large (1800 lines). I played around with the cobbler dhcp
management but I don't like they way it inserts the data.
Reply below...
here is a small section of my dhcpd.conf file. There are lots of
groups in the file.
group {
option routers 192.168.5.1;
option subnet-mask 255.255.255.0;
host linuxhost1 { hardware ethernet 00:02:0D:60:12:0C; fixed-address
192.168.5.48; }
host linuxhost12 { hardware ethernet 00:02:0D:60:12:0C; fixed-address
192.168.5.49; }
host linuxhost1y1 { hardware ethernet 00:02:0D:60:12:0C; fixed-address
192.168.5.50; }
host paylinuxhost1 { hardware ethernet 00:02:0D:60:12:0C;
fixed-address 192.168.5.51; }
host linuxhost3 { hardware ethernet 00:02:0D:60:12:0C; fixed-address
192.168.5.56; }
host linuxhostcvs1 { hardware ethernet 00:02:0D:60:12:0C;
fixed-address 192.168.5.69; }
host linuxhost-db1 { hardware ethernet 00:02:0D:60:12:0C;
fixed-address 192.168.5.139; }
host linuxhost-stg2 { hardware ethernet 00:02:0D:60:12:0C;
fixed-address 192.168.5.130; }
host linuxhost-ref1 { hardware ethernet 00:02:0D:60:12:0C;
fixed-address 192.168.5.131; }
host linuxhost-stg1 { hardware ethernet 00:02:0D:60:12:0C;
fixed-address 192.168.5.129; }
host linuxhost-app1 { hardware ethernet 00:02:0D:60:12:0C;
fixed-address 192.168.5.132; }
host linuxhostw1 { hardware ethernet 00:02:0D:60:12:0C; fixed-address
192.168.5.133; }
host linuxhost { hardware ethernet 00:02:0D:60:12:0C; fixed-address
192.168.5.134; }
host linuxhost-app1 { hardware ethernet 00:02:0D:60:12:0C;
fixed-address 192.168.5.136; }
host linuxhost-app2 { hardware ethernet 00:02:0D:60:12:0C;
fixed-address 192.168.5.137; }
host linuxhost-db2 { hardware ethernet 00:02:0D:60:12:0C;
fixed-address 192.168.5.138; }
}
When cobbler adds an entry it does the following:
host label1 {
hardware ethernet 00:50:56:ae:44:c5;
fixed-address 192.167.5.202;
next-server 192.168.0.1;
}
You're running an older cobbler version, it seems. In newer cobbler, if
you have the "hostname" field set on the object, label (which I've since
changed to just say "generic") will be replaced by the hostname in use.
As it appears you do have hostname info (at least in your manual setup),
hopefully this works for you.
The duplicate next-server entry is also removed in more recent versions.
I can't see anything against having a more consolidated file .... seems
like a sane thing to do to me.
Now, this is nice but when you have 2000 entries it gets quite messy.
Will the commands "cobbler sync" and "cobbler list" be able to handle
the large amount of entries?
Yes.
They should just take longer :)
Does anyone know how I can get cobbler to:
A. change label1 to the hostname
See above.
B. Get cobbler to remove the new lines
That's going to require a code change, but it can be done.
C. Determine which group to add the entry too based on IP address
Essentially:
https://hosted.fedoraproject.org/projects/cobbler/wiki/UsingCobblerDhcpManagementWithMultipleSubnets
So that it just adds a line like the following to the correct group
host linuxhost-db2 { hardware ethernet 00:02:0D:60:12:0C;
fixed-address 192.168.5.138; }
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
