Yoga Series Release Notes¶
20.1.0-25¶
New Features¶
OVN mechanism driver refuses to bind a port to a dead agent.
20.0.0¶
New Features¶
Add the shared field to security group API responses and support using shared as a query filter. For more information see bug 1942615.
Neutron now supports the placement enforcement for the guaranteed minimum bandwidth QoS rule type with direct-phyisical vnic_type as well. The data plane enforcement of such rule and vnic_type combination is still not supported.
Add
request_body
field to router callback event payloads. The field record the origin request body from user.
Add
BEFORE_UPDATE
callback event for router gateway.
Local IP - a virtual IP that can be shared across multiple ports/VMs (similar to anycast IP) and is guaranteed to only be reachable within the same physical server/node boundaries. The feature is primarily focused on high efficiency and performance of the networking data plane for very large scale clouds and/or clouds with high network throughput demands.
Added two new API methods to
QuotaDriverAPI
class.get_resource_usage
returns the current resource usage.quota_limit_check
checks the current resource usage of several resources against a set of deltas (a dictionary of resource names and resource counters).
Add support for VNIC type
remote-managed
in OVN. The OVN driver can now bind remote managed ports to SmartNIC DPUs. SmartNIC DPU portbinding requires OVN version 21.12 or above, compiled with OVN VIF version 21.12 or above.
Since this version, the support for stateless security groups is mandatory. The minimum OVN NB schema version must be 5.17.
Virtual ports are supported in OVN since version 2.12. Since Yoga, this support is mandatory. The minimum OVN SB schema version must be 2.5.
Report packet processing capacity on the OVS agent resource provider as the new
NET_PACKET_RATE_KILOPACKET_PER_SEC
,NET_PACKET_RATE_EGR_KILOPACKET_PER_SEC
orNET_PACKET_RATE_IGR_KILOPACKET_PER_SEC
resource inventory. This is similar to how the bandwidth resource is reported today. The former is used for non-hardware-offloaded OVS deployments, where packets processed from both ingress and egress directions are handled by the same set of CPU cores. Remaining inventories are used for hardware-offloaded OVS, where the incoming and outgoing packets are handled by independent hardware resources.
Added port-resource-request-groups API extension, that provides support for the new format of port’s
resource_request
andbinding:profile.allocation
attributes. The new format allows to request multiple groups of resources and traits from the same RP subtree.Assigning a new
QoS policy
withminimum_packet_rate
rule to analready bound port
updates the allocation in Placement.NOTE
: Placement allocation update is not supported if original QoS policy had nominimum_packet_rate
rule. Changing from direction-lessminimum_packet_rate
rule to a direction-orientedminimum_packet_rate
rule is not supported.
New configuration options for neutron-ovs-agent under section
[ovs]
:resource_provider_packet_processing_without_direction
,resource_provider_packet_processing_with_direction
andresource_provider_packet_processing_inventory_defaults
.resource_provider_packet_processing_without_direction
controls the minimum packet rate the OVS backend can guarantee in kilo (1000) packet per second.resource_provider_packet_processing_with_direction
is similar to the first option, but used in case the OVS backend has hardware offload capabilities. The last option can be used to tune the other fields (allocation_ratio
,min_unit
,max_unit
,reserved
,step_size
) of resource provider inventories.
Floating IP QoS network inheritance is now available for OVN L3 plugin QoS extension. If a network, hosting a floating IP, has a QoS associated, the floating IP addresses will inherit the network QoS policy and will apply on the OVN backend.
Added
qos-pps-minimum-rule-alias
API extension to enable GET, PUT and DELETE operations on QoS minimum packet rate rule without specifying policy ID.
Enabled placement enforcement for QoS minimum packet rate rule in OVS backend.
Added new API extension to QoS service plugin to support CRUD operations for minimum packet rate rule in Neutron server.
Added a check to verify if all rows of
ml2_port_bindings
table in the DB are using the new format forprofile
column. This check is part of upgrade check, that can be executed withneutron-status upgrade check
command. If some rows are using obsolete format, they can be sanitized with a script that can be executed withneutron-sanitize-port-binding-profile-allocation
command.
Upgrade Notes¶
A unique constraint for (network_id, network_type, physical_network) is added to the networksegments table. This was done to prevent race conditions on dynamic segment allocation. Operators having networks with multiple segments (e.g. when using hierarchical portbinding) should check that this constraint is not violated with the included upgrade-check.
Deprecation Notes¶
Config option
allow_overlapping_ips
is deprecated for removal now. Default value for that option is now changed to theTrue
in the default IPAM module of Neutron, as the only reason it was defaulting toFalse
was to keep compatibility with Nova security group code that was removed already. The config option itself will removed in theZ
release.
The
[agent] veth_mtu
parameter of ML2 OVS mechanism driver configuration has been deprecated. This parameter has had no effect since the Wallaby release.
Bug Fixes¶
Changes the API behaviour while using OVN driver to enforce that it’s not possible to delete all the IPs from a router port. For more info see bug LP#1948457
Support for the extensions
dns_domain_ports
andsubnet_dns_publish_fixed_ip
belonging to the DNS integration is now properly announced by the OVN driver. See bug 1947127
For IPv4 subnets when dns_nameservers is not set in the subnet, servers defined in ‘ovn/dns_servers’ config option or system’s resolv.conf are used, but for IPv6 subnets these are not used. The same will now be used for IPv6 subnets too. Additionally dns servers added in ‘ovn/dns_servers’ config option or system’s resolv.conf will be filtered as per the subnet’s IP version. For more info see the bug report 1951816.
Fixes bug 1943724.
The agent reporting state to the server now uses a RPC timeout set to the report_interval configuration option value. See 1948676.
Other Notes¶
Abstract method
plug_new
from the neutron.agent.linux.interface.LinuxInterfaceDriver now has additional positional argumentlink_up
. Usage of this method withoutlink_up
is now not possible. Third-party drivers which inherit from this base class now have to update the implementation of theirplug_new
method.
Class “PortBindingMixin” is removed. Last time this class was used in-tree was in Kilo release, in “N1kvNeutronPluginV2” and “SdnvePluginV2” classes. No active project is using it anymore. Table “portbindingports” is dropped from the database; it was used only in “PortBindingMixin”.
Any L3 agent extension must inherit from
neutron_lib.agent.l3_extension.L3AgentExtension
. TheL3AgentExtensionsManager
makes this check during the initial loading. AL3ExtensionException
will be raised if the condition is not met.
New service plugin and openvswitch agent extension could be configured in order to enable Local IP feature:
local_ip
OVN mechanism driver allows only to have one physical network per bridge.
It is assumed now that OVN supports Northbound table
Port_Group
by default. This table was added in the DB schema version 5.11. A sanity check is included if OVN is defined inml2.mechanism_drivers
configuration option.
OVN driver now uses stateless NAT for floating IP implementation. This allows to avoid hitting conntrack, potentially improving performance and also allowing to offload NAT rules to hardware.