On Thu, Dec 6, 2018 at 8:46 AM Sandro Emma <feeds.sandro(a)gmail.com> wrote:
we are running a RHV 4.1 installation which is working fine except one
We have a Network which is only used for fencing(power Management via
ilo), each host has an interface with this network and a custom ip, for
this to work we need a few custom routes.
At the moment we add the new routes via a plain route file under
/etc/sysconfig/network-scripts/, but the engine flags this interface then
How can we persist those changes across reboots and still be able to add
new devices via the UI ?
This looked promising but isnt working:
Thanks for any Help :)
I never used this feature, but I remember that you can specify in vdsm.conf
a list of interfaces that you want vdsm not to manage so that you can
configure them manually for your specific targets
Eg. on my 4.2.7 host I see this in the plain vdsm.conf.rpmnew
# Comma-separated list of fnmatch-patterns for host nics to be hidden
# from vdsm.
# hidden_nics = w*,usb*
# Comma-separated list of fnmatch-patterns for host bonds to be hidden
# from vdsm.
# hidden_bonds =
# Comma-separated list of fnmatch-patterns for host vlans to be hidden
# from vdsm. vlan names must be in the format "dev.VLANID" (e.g.
# eth0.100, em1.20, eth2.200). vlans with alternative names must be
# hidden from vdsm (e.g. eth0.10-fcoe, em1.myvlan100, vlan200)
# hidden_vlans =
In case you apply anything, I think you had better create a file in
/etc/vdsm/vdsm.conf.d, such as 50_unmanaged_nics.conf containing
hidden_nics = eth3
to be preserved across updates.
With this parameter you shouldn't see the interface listed in setup host
networks of the host gui.
The concept came out last year when I posted a question related to OVN and
Marcin Mirecki kindly answered about it.
See here and the whole thread:
Marcin, possibly you can add something for this particular need?