In many circumstances, there are only 2 interfaces on a given physical host. For most deployments, this means that the 2 interfaces will be bonded. I would like to request that the bonding configuration be available during the initial RHEV-H setup. For example, in configuring RHEV-H on a Cisco UCS blade, only the "VIC" card is available, and no one is going to waste one of the 2 10GbE interfaces just for the RHEVM network. Currently the rhevm network is configured on a single interface, then the remainder of the network config is completed post-"approval". This also involves extra steps to "sync the interface", then bond. Allowing the configuration of bonding during the initial configuration will save time and condense steps.
moving to rhel ovirt-node component
RHEV-H will probbaly support the creation of bonds during auto-install. What is missing is the automatic sync with RHEV-M.
BOOTIF=bond* bond_setup=bond*:ethX,ethX is supported on 6.5 base image(ovirt-3.0.1-16.el6_5, rhevh-6.5-20140110.1) Adding Pavel(pstehlik@) in CC list to let him know this bug also related RHEV build testing.
Tested as follows using a rhevh base image: 1. Boot with BOOTIF=bond0 bond_setup=bond0:eth0,eth1 storage_init adminpw=... 2. Wait for auto-install to complete Results: 1. Check on status page: bond0 is shown 2. Check network page: bond0 is shown as configured
(In reply to Fabian Deutsch from comment #10) > Tested as follows using a rhevh base image: > > 1. Boot with BOOTIF=bond0 bond_setup=bond0:eth0,eth1 storage_init adminpw=... > 2. Wait for auto-install to complete > > Results: > 1. Check on status page: bond0 is shown > 2. Check network page: bond0 is shown as configured tested the auto1032 build, auto install with BOOTIF=bond0 bond_setup=bond0:eth0,eth1 storage_init adminpw= after install complete, the bond0 is shown on status page as connected and shown as configured in network page.
tested the rhev-hypervisor6-6.6-20141107.0.iso, auto install with BOOTIF=bond0 bond_setup=bond0:eth0,eth1 storage_init adminpw= after install complete, the bond0 is shown on status page as connected and shown as configured in network page.
tested the rhev-hypervisor7-7.0-20141107.0.el7ev, change auto install bond parameter > https://bugzilla.redhat.com/show_bug.cgi?id=1156343 > comment 2 to auto-install with 'BOOTIF=bond0 bond_setup=bond0:ens3 bond=bond0:ens3 storage_init adminpw=' after install complete, the bond0 is shown on status page as connected and shown as configured in network page.
tested the rhev-hypervisor6-6.6-20141119.0.el6ev auto install with BOOTIF=bond0 bond_setup=bond0:eth0,eth1 storage_init adminpw= after install complete, the bond0 is shown on status page as connected and shown as configured in network page.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2015-0160.html