Network Segment Range Management

Registered by Kailun Qin on 2018-09-05

Currently, network segment ranges are configured as an entry in ML2 config file [1]_ that is statically defined for tenant network allocation and therefore must be managed as part of the host deployment and management. When a normal tenant user creates a network, Neutron assigns the next free segmentation ID (VLAN ID, VNI etc.) from the configured segment ranges; only an administrator can assign a specific segment ID via the provider extension.

This spec introduces an extension which exposes the segment range management to be administered via the neutron API. In addition, it introduces the ability for the administrator to control the segment ranges globally or on a per-tenant basis.

[1] /etc/neutron/plugins/ml2/ml2_conf.ini

Blueprint information

Status:
Complete
Approver:
None
Priority:
High
Drafter:
Kailun Qin
Direction:
Approved
Assignee:
Kailun Qin
Definition:
Approved
Series goal:
Accepted for stein
Implementation:
Implemented
Milestone target:
milestone icon stein-3
Started by
Miguel Lavalle on 2018-12-10
Completed by
Kailun Qin on 2019-04-05

Related branches

Sprints

Whiteboard

Addressed by: https://review.openstack.org/599980
    Network Segment Range Management

Gerrit topic: https://review.openstack.org/#q,topic:bp/network-segment-range-management,n,z

Addressed by: https://review.openstack.org/624708
    Support Network Segment Range CRUD as extensions

Addressed by: https://review.openstack.org/624709
    Use network segment ranges for segment allocation

Addressed by: https://review.openstack.org/626162
    Add API test for network segment range extension

Addressed by: https://review.openstack.org/626500
    Add network-segment-range extension API definition

Addressed by: https://review.openstack.org/626866
    Extend methods for network segment range support

Addressed by: https://review.openstack.org/627226
    Add `default` to network segment range resource

Addressed by: https://review.openstack.org/627299
    api-ref: document network-segment-range extension

Addressed by: https://review.openstack.org/629422
    Fix key type of `used` dict in JSON responses

Addressed by: https://review.openstack.org/629423
    Fix inconsistent `shared` attribute default value

Addressed by: https://review.openstack.org/631219
    Move network segment range types to lib constants

Addressed by: https://review.openstack.org/636990
    Add exception to prevent overlapped segment ranges

Addressed by: https://review.openstack.org/637006
    Add methods for network segment range support

Addressed by: https://review.openstack.org/638386
    Devstack plugin for network-segment-range api

Addressed by: https://review.openstack.org/639028
    Add NETWORK_SEGMENT_RANGE plugin constant

Addressed by: https://review.openstack.org/639110
    [doc] Add network segment ranges into admin guide

Addressed by: https://review.openstack.org/640633
    standard-attr for network-segment-range api-ref

Addressed by: https://review.openstack.org/640777
    Change exception types in network_segment_range

Addressed by: https://review.openstack.org/643882
    Adds revision description for network_segment_range

Gerrit topic: https://review.openstack.org/#/q/topic:bp/network-segment-range-management

Addressed by: https://review.openstack.org/653666
    Use segment range exceptions from neutron-lib

Gerrit topic: https://review.opendev.org/#/q/topic:bp/network-segment-range-management

Addressed by: https://review.opendev.org/653666
    Use segment range exceptions from neutron-lib

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.