neutron/releasenotes/notes/add-network-segment-range-extension-0893a67cbf3f10fe.yaml
Kailun Qin 563a536d02 Support Network Segment Range CRUD as extensions
This patch adds the support for network segment range CRUD. Subsequent
patches will be added to use this network segment range on segment
allocation if this extension is loaded.

Changes include:
- an API extension which exposes the segment range to be administered;
- standard attributes with tagging support for the new resource;
- a new service plugin "network_segment_range" for the feature
  enabling/disabling;
- a new network segment range DB table model along with operation
  logic;
- Oslo Versioned Objects for network segment range data model;
- policy-in-code support for network segment range.

Co-authored-by: Allain Legacy <Allain.legacy@windriver.com>

Partially-implements: blueprint network-segment-range-management
Change-Id: I75814e50b2c9402fe6776229d469745d7a72290b
2019-03-07 08:20:30 +00:00

26 lines
1.3 KiB
YAML

---
prelude: >
Added support for network segment range management. This introduces the
ability for administrators to control the segment ranges globally or on
a per-tenant basis via the Neutron API.
features:
- |
Before Stein, network segment ranges were configured as an entry in ML2
config file ``/etc/neutron/plugins/ml2/ml2_conf.ini`` that was statically
defined for tenant network allocation and therefore had to be managed as
part of the host deployment and management.
The new ``network-segment-range`` API extension has been introduced, which
exposes the network segment ranges to be administered via API. This
allows users with admin privileges to be able to dynamically manage
the shared and/or tenant specific network segment ranges.
Standard attributes with tagging support are introduced to the new
resource.
The feature is controlled by the newly-added service plugin
``network_segment_range``.
A set of ``default`` network segment ranges will be created out of
the ranges that are defined in the host ML2 config file
``/etc/neutron/plugins/ml2/ml2_conf.ini``, such as
``network_vlan_ranges``, ``vni_ranges`` for ml2_type_vxlan,
``tunnel_id_ranges`` for ml2_type_gre and ``vni_ranges`` for
ml2_type_geneve.