RHEV 3.2 hypervisor networking configuration functionality issues and omissions

Issue

RHEV 3.2 hypervisor networking issues and functionality omissions that cause problems for us and for which we need solutions.

• The ifcfg files on the hypervisor for physical interfaces generated by RHEV have the 'HWADDR' mac address field in them. We need that to not happen. Through biosdevnames and previous techniques we already guarantee that NIC names will remain consistent across boot and this breaks our operational practices.

• I don't see a way to specific the 'ETHTOOL_OPTS' field for physical interfaces under control of RHEV. We must be able to control this and I'm not sure if it will even work out well if it has to go through RHEV. This could be a general need that must be solved by hooks into the hypervisor network config layer, yet I don't see any VDSM hook events for this type of thing.

• We must be able to configure the BRIDGING_OPTS field on bridge interfaces.

• The standard bond types don't appear to let you configure the BONDING_OPTS field. Maybe this can be solved by the "Custom" bond type?