> cobbler takes dhcp.template and creates /etc/dhcpd.conf with it > just fine. > > There has to be a subnet-entry thou for each network segment the > deployed servers are coming up from. Until now we manually edit > dhcp.template for this. > > Isnt all required data for this already in the 'cobbler system' > object? Cobbler could check if the subnet we want to boot from > is already in the dhcp.template or create such an entry in the > final dhcpd.conf . > > Maybe its already doing this but i am missing the peaces?
A feature that didn't make it into 2.0 was network objects, which would pretty much be required for creating new subnets for the dhcpd.conf. Otherwise, we'd have to scan through every system object and built a list of subnets, something that's not really practical if you have a large system base. I had done a little work on the network stuff, mainly webui based, but when it was decided to exclude that I stopped working on it, and I'm not sure anyone has picked it back up. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
