[FFe] Update OVN to new 23.09.0 upstream version
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ovn (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
As detailed in an upstream announcement [0], the OVN 23.09.0 release was delayed. It was released as scheduled on Friday September 15th [1] and the upstream NEWS file has been updated accordingly [2].
This new upstream version includes fixes performance improvements and new features that are important for our community, and we would like to include it in the Ubuntu Mantic release.
OVN 23.09.0 has been uploaded to Debian unstable [3][4].
The package can also be viewed in a PPA for details on how it would look on Ubuntu [5].
As soon as the package has been uploaded to Debian unstable we would like to sync it to Mantic.
0: https:/
1: https:/
2: https:/
3: https:/
4: https:/
5: https:/
CVE References
Changed in ovn (Ubuntu): | |
importance: | Undecided → High |
description: | updated |
description: | updated |
Hi,
Thanks for filing an FFe. I think this broadly makes sense and ovn releases are pretty stable and tested. As for now, I see the following changelog entries:
Post v23.06.0 age_threshold" .
-------------
- Added FDB aging mechanism, that is disabled by default.
It can be enabled per logical switch with other_config
"fdb_
- Add DHCPv6 "fqdn" (39) option, that works similarly to
DHCPv4 "hostname" (12) option.
- Support to create/update MAC_Binding when GARP received from VTEP (RAMP)
switch on l3dgw port.
- To allow optimizing ovn-controller's monitor conditions for the regular
VIF case, ovn-controller now unconditionally monitors all sub-ports
(ports with parent_port set).
- ECMP routes use L4_SYM dp-hash by default if the datapath supports it.
Existing sessions might get re-hashed to a different ECMP path when
OVN detects the algorithm support in the datapath during an upgrade
or restart of ovn-controller.
Given this is not yet final, I don't think we can take that call right now. I mean, as I said, in broader terms it should be OK but how about this - once this is released and the changelog is finalized, we can circle back on this and take a decision?
Feel free to ping me or release team members on IRC and we'll take another look.
Just to be clear - I am not an official release team member yet. :)