Queens Series Release Notes¶
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>_.
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.
When the ivs interface (or nfvswitch) configuration changes, ivs (or nvfswitch) needs to be restarted in order to pick up the new configuration.
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.
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.
Adding dpdk support in meallnox nics. Dpdk now fully suuported in mellanox nics.
sriov_pf and sriov_vf object types are added to allow configuration and usage of the SR-IOV PF and VF devices in the host machine. The sriov_config service file shall be used to reconfigure the SR-IOV devices after reboots. VLAN suport for SR-IOV VF device is not available in this patch.
Getting the ordered, active, and available nics has been traditionally one of the parts of os-net-config that can cause issues due to either user error or bugs. There are helpful log messages to log what is going on in the logic, but it’s all hidden behind the DEBUG log level. These messages should be INFO instead of DEBUG. It’s much more user friendly when there are issues instead of having to rerun with –debug.
os-net-config always logs the message “Using mapping file at: /etc/os-net-config/mapping.yaml” even if the file does not exist, in which case it’s not actually being used at all. Move the log message to only be shown if the mapping file actually exists and is used. In the case where no mapping file is used, also log a message indicating such.