This is a useage question i think. Historically bonds have been applied by snippets in %post but to me it seems to make most sense to have cobbler handle it natively now that it seems to be able to.
Lets say we have a box with 4 nics and those nics make 2 bonds - is it possible that this box can still do a DHCP and PXE off just 1 interface at install time as i presume you need to PXE/DHCP to a real interface as opposed to a bond? How is this handled within cobbler as i see the bonds seem to be sorted out in the post_network_config snippet so i am just wondering how this all works in practice?
thanks
On 04/03/2009 12:24 PM, Tom Brown wrote:
This is a useage question i think. Historically bonds have been applied by snippets in %post but to me it seems to make most sense to have cobbler handle it natively now that it seems to be able to.
Lets say we have a box with 4 nics and those nics make 2 bonds - is it possible that this box can still do a DHCP and PXE off just 1 interface at install time as i presume you need to PXE/DHCP to a real interface as opposed to a bond? How is this handled within cobbler as i see the bonds seem to be sorted out in the post_network_config snippet so i am just wondering how this all works in practice?
New in cobbler 1.6, this should work as expected. Basically any of the interfaces in the bond that dhcp will get the ip address of the bonded interface. It should then do PXE as expected. If you setup the bonding as documented on the wiki and in the included documentation, the dhcp configs should get setup so that either interface can dhcp and get the correct ip.
On 04/03/2009 06:34 PM, Scott Henson wrote:
On 04/03/2009 12:24 PM, Tom Brown wrote:
This is a useage question i think. Historically bonds have been applied by snippets in %post but to me it seems to make most sense to have cobbler handle it natively now that it seems to be able to.
Lets say we have a box with 4 nics and those nics make 2 bonds - is it possible that this box can still do a DHCP and PXE off just 1 interface at install time as i presume you need to PXE/DHCP to a real interface as opposed to a bond? How is this handled within cobbler as i see the bonds seem to be sorted out in the post_network_config snippet so i am just wondering how this all works in practice?
New in cobbler 1.6, this should work as expected. Basically any of the interfaces in the bond that dhcp will get the ip address of the bonded interface. It should then do PXE as expected. If you setup the bonding as documented on the wiki and in the included documentation, the dhcp configs should get setup so that either interface can dhcp and get the correct ip.
In addition, the pre_install_network_config picks one of the bond's devices and configures the IP information on it. I've been working on falling back to the second if the first interface is down, but I need to continue work on that some time (unfortunately, %pre stuff is hard to debug).
Jasper
cobbler@lists.fedorahosted.org