Jasper Capel wrote: > Hey all, > > Now that the arbitrary interface name and VLAN stuff is done, I'd like > to add bonding support to Cobbler. I'd like to start with coming to an > agreement on how this should look from a CLI-perspective. > > I'd suggest the following: > > cobbler system edit --name=system1 --add-interface=bond0 > --bonding=master --bonding-opts="miimon=100" --ip=192.168.0.1 > --subnet=255.255.255.0 --gateway=192.168.0.254 --static=1 > cobbler system edit --name=system1 --add-interface=slave0 > --mac=aa:bb:cc:dd:ee:f0 --bonding=slave --bonding-master=bond0 > cobbler system edit --name=system1 --add-interface=slave1 > --mac=aa:bb:cc:dd:ee:f1 --bonding=slave --bonding-master=bond0 > > I'd like to hear your thoughts on this. :)
This sort of thing looks good to me. I'd also like to see support for bridges. For example, for a CentOS 5.2 machine with xen 3.3, I use the following network scripts to create a bridge for the DomU guests to use: # Intel Corporation 82573E Gigabit Ethernet Controller (Copper) DEVICE=eth0 HWADDR=00:30:48:90:FB:B6 ONBOOT=yes BRIDGE=br0 DEVICE=br0 TYPE=Bridge BOOTPROTO=static DHCPCLASS= IPADDR=192.168.1.30 NETMASK=255.255.255.0 ONBOOT=yes DELAY=0 I'd like to be able to specify this in my cobbler set up. The only major differences between these and "normal" NIC configurations are: - the physical device has no IP configuration - the physical devices has "BRIDGE=br0" - the bridge has TYPE=Bridge <-- This is stupidly case-sesnsitive! - I'm not sure what DELAY=0 does! This style of config is taken from http://wiki.libvirt.org/page/Networking R. _______________________________________________ cobbler mailing list [email protected] https://fedorahosted.org/mailman/listinfo/cobbler
