f628905279
Since [1], the physical network VLAN ranges parser populates the ranges for those entries without a defined range, allowing all valid VLAN ranges ([1, 4094]). Some VLAN driver tests, relying on the previous implementation, considered that the physical network without a defined VLAN range does not have segments to allocated (those segments are created on the fly by "SegmentTypeDriverallocate_fully_specified_segment). Since [1], all physical network segments are stored in the "ml2_vlan_allocations" table and set as non allocated. This patch also reverts [2]. When the physical networks are defined in "network_vlan_ranges", there is no distinction between tenant and provided networks; the physical network segments are assigned by the user. It is possible to create a provider network without defining the segmentation ID, it will be provided by the Neutron VLAN driver, if there are free segments for the required physical network. [1]https://review.opendev.org/c/openstack/neutron-lib/+/779515 [2]1376df7873c2ac77c256ab2fed928de41a2c1d58 Closes-Bug: #1919280 Related-Bug: #1918274 Related-Bug: #1649750 Change-Id: I191e020ddb97dcf8fb41139d35bfd699e125379b |
||
|---|---|---|
| .. | ||
| ml2 | ||
| __init__.py | ||