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