[RFE] Support creating a subnet without an allocation pool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Wishlist
|
Unassigned | ||
python-openstackclient |
New
|
Undecided
|
Sindhu Devale |
Bug Description
Problem Description
===================
Currently, subnets are created with an allocation pool(s) that is either a) user-defined or b) automatically generated based on CIDR. This RFE asks that the community support the creation of subnets without an allocation pool.
Neutron allows users to create ports using fixed IP addresses that fall outside of the subnet allocation pool(s) but within the range defined by the CIDR. Neutron keeps track of assigned addresses and does not allow for overlap within the same subnet.
Use cases:
* An external IPAM service is utilized that is not integrated with OpenStack/Neutron. The user wants to create a port with a specific IP address using the --fixed-ip flag, and does not want Neutron automatically consuming addresses from the pool if an address is not manually allocated via Neutron or Nova.
Proposed Change
===============
Allow 'None', or similar value, as a valid start/end value. The result would be that Neutron would not create an allocation pool for the subnet. The Neutron client would have a new flag, such as --no-allocation
As I see it, not creating an allocation pool for a subnet would mean that when a port is created without an IP specified, Neutron would return the 'no more addresses available for allocation' error. Otherwise, the current behavior of allowing the user to specify a particular fixed IP address remains the same.
tags: | added: rfe |
tags: | added: l3-ipam-dhcp |
Changed in python-openstackclient: | |
assignee: | nobody → Sindhu Devale (sindhu-devale-3) |
Bear in mind that we're getting super busy in time for feature freeze, and we're not processing RFEs at this point.