2023.1 Series Release Notes

2023.1-eom

Bug Fixes

  • [bug 2072754] Fixed maintenance task that was breaking IPv4 load balancers with health monitors.

4.0.2

Known Issues

  • Load Balancer Health Check for Floating IPs are not populated with the protocol port. At this way, when a backend is detected on ERROR state requests to the Floating IP are still distribute to the ERROR’ed members. In order to fix the existing Load Balancer Health Checks it is required to recreate the entire Octavia Health Monitor, which will recreate the associated OVN Load Balancer Health Check(s).

Upgrade Notes

  • In order to support the new ‘device_owner’ for OVN Load Balancer Health Monitor ports this version requires a Neutron version > 23.0.0rc2

Bug Fixes

  • [bug 1997418] Added the protocol port to the Load Balancer Health Check associated with the Floating IP, additional fields have been introduced to the external_ids to provide more accuracy information about the entities affected by any change over the Floating IP or LB VIP.

  • A maintenance task process has been added to update the existing OVN LB HM ports to the new behaviour defined. Specifically, the “device_owner” field needs to be updated from network:distributed to ovn-lb-hm:distributed. Additionally, the “device_id” will be populated during update action.

Other Notes

  • A maintenance task thread has been added to work on periodic and one-shot tasks that also allows the future changes to perform the needed upgrades actions.

3.0.0

Upgrade Notes

  • Python 3.6 & 3.7 support has been dropped. The minimum version of Python now supported is Python 3.8.

2.0.0

Bug Fixes

  • Creating members without specifying a subnet ID is now supported. Since the subnet ID is an optional API argument, if not given the provider driver will now attempt to look it up via the pool ID that is a required argument.

1.1.0

New Features

  • The OVN Octavia provider drvier now supports health monitoring. TCP and UDP Connect health monitors are now supported by the provider driver, when the underlying OVN version supports them. The health monitor uses the OVN distributed DHCP port as the source IP for messages by default, if one doesn’t exist then a port will be created on each given subnet. The list of member ports to monitor is updated whenever one is created or deleted.

1.0.0

New Features

  • Add support for the SCTP protocol in the OVN provider driver.

0.1.0

Prelude

OVN Octavia provider driver has been created from the networking-ovn repository.

Upgrade Notes

  • OVN Octavia Provider driver registers under the same entry point. There is no action to be done from operator side.

Bug Fixes

  • OVN Octavia provider driver now supports both TCP and UDP pool/listener protocols configured in the same Octavia Load Balancer.