ML2 driver should only support geneve and vlan tenant network types
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-ovn |
Fix Released
|
Undecided
|
Richard Theis |
Bug Description
OVN supports "geneve" and "vlan" network types for neutron tenant networks. However, the default DevStack deployment sets the tenant_
For geneve tenant networks, we'll need to determine the proper defaults for the vni_ranges and max_header_size options under [ml2_type_geneve] in ml2_conf.ini. Since OVN doesn't allow configuration of the vni, it should be ignored (possibly logged) when creating geneve tenant networks.
For vlan tenant networks, the VLAN ID should be used when creating the network. This is similar to vlan provider networks. We'll also need to determine the proper defaults for the network_vlan_ranges option under [ml2_type_vlan] in ml2_conf.ini.
The result for this bug fix should be documented as appropriate.
Changed in networking-ovn: | |
assignee: | nobody → Richard Theis (rtheis) |
summary: |
- ML2 should only support geneve and vlan tenant network types + ML2 driver should only support geneve and vlan tenant network types |
description: | updated |
How do we handle VXLAN provider networks for L3GW/VTEP?