yahoo-eng-team team mailing list archive

[Armando Migliaccio <1616208@xxxxxxxxxxxxxxxxxx>]

We should see if the OSC client allows the specification of *no
allocation pools* as suggested by Carl on comment #5. Excerpt below:

For now, you can work around this by creating the subnet and then
following up with PUT to
http://{{neutron_ip}}:9696/v2.0/subnets/{{subnet_id}} with this in the
body:

  {"subnet": {"allocation_pools": []}}

I doubt the client supports this yet. So, maybe someone could enhance
the client to allow this.

** Also affects: python-openstackclient
   Importance: Undecided
       Status: New

** Changed in: neutron
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1616208

Title:
  [RFE] Support creating a subnet without an allocation pool

Status in neutron:
  Invalid
Status in python-openstackclient:
  New

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-pool, or something similar.

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1616208/+subscriptions