Fix invalid bond mode SRU regression (LP: #1877643)
netplan < 0.98 accepted invalid bond modes, we should _not_ reject such
configs, even though they are invalid, to avoid regressions in stables releases.
This affects the bionic stable release, as the original version in this
release shipped netplan < 0.98.
SR-IOV support for explicitly defining the VF count (#130)
This is a possible feature request to the just-landed SR-IOV support in netplan. This PR introduces an optional 'virtual-function-count:' parameter that can be defined for physical functions to force the allocation of a given number of VFs, regardless of how many are actually used in the netplan config. There are of course safety checks to ensure that we can't request less VFs than actually needed in netplan.
This feature request came from the OpenStack team. We did consider such a thing originally, but then decided that it's better if we let netplan handle it. This PR adds this as an option (not recommended for everyday usage tho).
This might still need some work, but at least the base support is here.
This adds support for SR-IOV devices. One can now define VFs for given PFs via a 'link:' tag. Netplan then will create those dynamically on netplan apply. We also have a quick framework in case some special devices need a module unload+load to get the changes deployed.
This also adds support for SR-IOV hardware VLAN tagging via the renderer: sriov syntax.
The "wifi.seen-bssids" setting is deprecated.
NetworkManager will not read this option or use it internally.
Instead, it reads this data from it's internal state db at:
/var/lib/NetworkManager/seen-bssids
This is why we do not need to support this field for netplan.io