Bug 1955123 - [ovn][migration] 4K ports/networks validation before migrating to ML2/OVN if the target overlay is VXLAN [NEEDINFO]
Summary: [ovn][migration] 4K ports/networks validation before migrating to ML2/OVN if ...
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: beta
: ---
Assignee: OSP Team
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-29 13:39 UTC by Daniel Alvarez Sanchez
Modified: 2023-07-23 04:19 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:
gurpsing: needinfo? (dalvarez)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-3485 0 None None None 2021-11-18 15:05:46 UTC

Description Daniel Alvarez Sanchez 2021-04-29 13:39:22 UTC
The VXLAN implementation for ML2/OVN poses a limitation of 4K networks and 4K ports per network. If the user selects VXLAN as the target overlay for the ML2/OVN migration, the migration process should validate that the cloud is suitable before attempting the migration. If it doesn't qualify, the user needs to reconsider the migration or use Geneve as the target overlay.

Please, note that for the validation, VLAN and flat networks must be excluded from the 4K limits.

There should be also a warning and the control plane should be fenced to avoid creating resources beyond the limits between the validation and the migration itself.


Note You need to log in before you can comment on or make changes to this bug.