3796c03fd1
Fixed the queries to retrieve the segment ID allocations when service plugin network_segment_range is enabled. With the previous implementation, a project user was able to allocate a segment ID belonging to other project segment range. The solution implemented was discussed in [1]: - A project user will retrieve segments from the project ranges. - When depleted, the segment IDs will be retrieved from the shared range, never using another project segment ID. [1]http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012736.html Conflicts: neutron/objects/network_segment_range.py neutron/objects/plugins/ml2/base.py neutron/objects/plugins/ml2/vxlanallocation.py neutron/objects/plugins/ml2/vlanallocation.py neutron/tests/unit/objects/test_network_segment_range.py Change-Id: I953062d9ee8ee5ee9a9f07aff4a8222ac63ed525 Closes-Bug: #1863423 (cherry picked from commit |
||
---|---|---|
.. | ||
plugins | ||
README | ||
__init__.py | ||
address_scope.py | ||
agent.py | ||
allowed_address_pair.py | ||
data_plane_status.py | ||
dns.py | ||
dvr.py | ||
external_net.py | ||
flavor.py | ||
l3.py | ||
l3_attrs.py | ||
l3agent.py | ||
l3ha.py | ||
loggingapi.py | ||
metering.py | ||
network_segment_range.py | ||
port_forwarding.py | ||
portbinding.py | ||
provisioning_block.py | ||
securitygroup.py | ||
segment.py | ||
servicetype.py | ||
subnet_service_type.py | ||
tag.py | ||
uplink_status_propagation.py |
README
This directory is designed to contain all SQLAlchemy models shipped with core Neutron. * The expected directory structure is flat, except for the ML2 plugins. All ML2 plugin models should fall under the plugins subdirectory (i.e. plugins/ml2/gre_allocation). * Module names should use singular forms for nouns (port.py, not ports.py).