Christopher Johnston wrote: > Just going through a feature that I think has some value with cobbler, > when adding an interface to cobbler we may not want every interface to > be added to our dhcp configs. Not only does that create a huge > dhcpd.conf with uncessary entries, but it also adds interfaces that > may be blank or missing --dns-name (they get added as genericXnn). It > would be useful to have an option that says --dhcp (1|2) so only those > interfaces are added to the DHCP configuration. The default could > always be "true" which is most likely good for most environments. > This would allow greater flexibility for the type interfaces that we > add. I know there is a --static option, but I dont believe that works > as advertised as even on the latest (1.6 version) of cobbler I am > still seeing entries get added called genericXnn. > > -Chris
Various points: If using DHCP management, non-managed interfaces can be flagged as static and shouldn't show up. (Please file a bug on this as that's clearly broken if so) Bonded interfaces also don't show up. If they don't have a MAC assigned, they should be allocated out of the free range pool, if we add an entry for something that doesn't have a MAC filed in, that should be a bug. Does this happen? I don't like the idea of adding another flag when the logic should basically do the right thing with the data that is there. (A bug fix isn't a reason to add another flag when the problem could be fixed elsewhere, right?) --Michael _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
