Comment 12 for bug 1728134

I do not think that we necessarily need OpenVSwitch support in netplan.io. As daxtens pointed out, OpenVSwitch uses a persistent configuration database and thus does not fit well into the concept of netplan.io anyway.

I think it is okay, if OpenVSwitch needs to be configured through its own channels (ovs-vsctl). The main problem at the moment is that netplan.io does not provide a way to bring an interface up without configuring an address for that interface. However, if an interface is part of an OpenVSwitch bridge, it needs to be brought up in order for the bridge to work as expected.

In systemd-networkd, this can easily be solved by adding a configuration file like the following:

[Match]
Name=eth0

[Network]
DHCP=no
IPv6AcceptRA=no
LinkLocalAddressing=no

In this example, the configuration is for eth0, but of course this will work for other interfaces too. What we really need in my opinion is a way to tell netplan.io that it shall generate such a configuration file.

The first step would be generating a configuration file, even if DHCPv4 and DHCPv6 are disabled, no RAs are accepted, and there is no static address either. This would only leave the "LinkLocalAddressing" option as a new feature because netplan.io does currently not provide a matching option.

Does anyone know whether the same functionality can also be achieved with NetworkManager as the backend?