I was looking over the contents of post_install_network_config in the
devel branch of cobbler and it looks pretty good. The idea that one
wants to setup VLANs or bonding as part of the post-install process is a
good one.
Anyway, there are a few changes that I'd propose though for RHEL/Centos5
and Fedora and several that would be needed to make RHEL/Centos4 work
correctly.
For RHEL/Centos5 and Fedora the bonding parameter 'max_bonds' in
modprobe.conf isn't really needed, so it can be dropped.
--- a/snippets/post_install_network_config
+++ b/snippets/post_install_network_config
@@ -48,16 +48,6 @@
## end looping through the interfaces to see which ones we need to configure.
## =============================================================================
-
- #set $i = 0
-
- ## setup bonding if we have to
-
- #if $numbondingdevs > 0
- echo "options bonding max_bonds=$numbondingdevs" >>
/etc/modprobe.conf
- #end if
-
- ## =============================================================================
## create a staging directory to build out our network scripts into
## make sure we preserve the loopback device
For RHEL/Centos4 the bonding options will need to be placed in
/etc/modprobe.conf rather than in ifcfg-bondX files.
--- a/snippets/post_install_network_config
+++ b/snippets/post_install_network_config
@@ -189,9 +179,7 @@
#if $bonding.lower() == "master" and $bonding_opts != ""
## configure bonding if required
- cat >> $devfile << EOF
- BONDING_OPTS="$bonding_opts"
- EOF
+ echo "options $iname $bonding_opts" >>
/etc/modprobe.conf.cobbler
#end if
echo "ONPARENT=yes" >> $devfile
In general the VLAN stuff looks good too, but it would be hard to know
for sure without testing it pretty well.
Long term it would be great to support VLANs on bonded interfaces, but
there are not a bunch of people doing that right now (and I didn't write
any patches, so I should probably shutup :), so it's probably not a
priority.
-andy