Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1042425

Summary: [RFE][neutron]: Add the ability to update the IP allocation pool range for a subnet.
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/neutron/+spec/make-allocation-pool-updatable
Whiteboard: upstream_milestone_none upstream_status_not-started upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 16:49:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description RHOS Integration 2013-12-12 22:14:25 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/make-allocation-pool-updatable.

Description:

It is not unusual for users to create a subnet but only use a small subset of the subnet for the allocation pool.  For instance the user could limit the allocation pool to a set of IPs that have DNS names associated.  It is equally, likely, however for the user to later have to extend the allocation pool to meet a growing number of VMs.  There is not, at the moment, a solution that allows the user to extend the existing allocation pool to meet the growing need.  This BluePrint proposes adding the ability to extend (and possibly) contract an allocation pool's range of IP addresses.

Specification URL (additional information):

None