Comment 7 for bug 1863423

Reviewed: https://review.opendev.org/712508
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bbe401aaf9bfdd77e1d43d547b2cdb436b1440c8
Submitter: Zuul
Branch: stable/train

commit bbe401aaf9bfdd77e1d43d547b2cdb436b1440c8
Author: Rodolfo Alonso Hernandez <email address hidden>
Date: Wed Feb 26 10:39:19 2020 +0000

    Fix queries to retrieve allocations with network_segment_range

    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/vlanallocation.py
        neutron/objects/plugins/ml2/vxlanallocation.py

    Change-Id: I953062d9ee8ee5ee9a9f07aff4a8222ac63ed525
    Closes-Bug: #1863423
    (cherry picked from commit 046672247de56bad950e8267a57bd26205f354a0)