Stein Series Release Notes¶
Adding PCI address of each VF to sriov_config.yaml. This information could be used in deriving the PCI passthrough whitelist.
A key called “domain” is now available for interfaces. This allows the setting of a domain for an ifcfg configuration, which will aide DNS search.
Support for configuring policy-based routing has been added. A new top-level object “route_table” has been added, which allows the user to add tables to the system route table at /etc/iproute2/rt_tables. Routes have a new “table” property for specifying which table to apply the route. Interfaces now have a “rules” property that allows the user to add arbitrary rules for when the system should use a particular routing table, such as input interface or source IP address.
Some changes can now be made to interfaces without restarting. Changes to routes, IP addresses, netmask, or MTU will now be applied using iproute2 without restarting the interface, and the ifcfg file will be updated.
Since this change uses iproute2 to make changes to live interfaces, it does not allow MTU on DPDK interfaces to be modified in place. DPDK requires that ovs-vsctl be run to modify MTU. For DPDK interfaces, MTU changes will result in an interface restart.
The ovs-appctl command may fail, particularly when setting an interface as a slave in a bond if the primary interface is not yet up. Retry the ovs-appctl command and log a failure if the command still fails.
The schema now allow the
routesoption to be an empty list. (Previously at least one route was was required.) Bug: 1792992 <https://bugs.launchpad.net/os-net-config/+bug/1792992>_.
When the ivs interface (or nfvswitch) configuration changes, ivs (or nvfswitch) needs to be restarted in order to pick up the new configuration.