A while back Robin Bowes contributed a snippet on the Wiki that was 
intended to allow the IP/MAC information used for static cobbler setups 
to be better used to auto-generate the "network" lines in a kickstart file.

I have reworked this snippet to make it more useful for the DHCP case, 
and in addition have added the "--static=0/1" option to Cobbler system 
objects.   This makes it now possible for cobbler system objects to have 
a mixture of static and DHCP interfaces and have them all templated out 
in the kickstart file correctly.

This is described here:   
https://fedorahosted.org/cobbler/wiki/CobblerNetworkTemplatingForKickstart

The "sample*.ks" kickstart templates will be edited such that they all  
use this new "SNIPPET::network_config" code.    If such code is used for 
a profile based install, it will just provide one DHCP interface, so 
static cobbler users are advised to use all system records (as was 
really the case before with the other static setup snippet).

Anyway, this finally brings this feature into the mainstream.  I'll also 
be adding the "static Y/N" boolean to the cobbler interface editor in 
the Web app.

Hopefully this is useful for all static-IP shops that are tired of 
fighting somewhat with Anaconda as well as doing their own Cheetah 
templating for that.

For those that don't understand this, you can ignore it, though it will 
be the default for new users and they should find it "just works".

If someone has a cobbler system record and they do not define any 
interfaces as static they will always get at least one DHCP interface so 
it all works out of the box.

This is on the devel branch now for those that would like to check it 
out, I'm still editing the snippets and web app.

--Michael




_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler

Reply via email to