yahoo-eng-team team mailing list archive

[Ryan Tidwell <1558812@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

It is currently not possible to take an existing subnet and move it into
a subnetpool or address scope.  The subnetpool_id attribute on subnets
is not updateable, meaning that once a subnet is created it cannot be
moved between subnetpools or address scopes.  If a subnet was created
without a subnetpool_id, it still cannot be moved into a subnetpool or
address scope.  This is a barrier to the adoption features like
subnetpools, address scopes, and BGP.  Many users likely have existing
subnets that they would prefer to not destroy and re-create just for the
purpose of being able to use these features.

This RFE proposes making the subnetpool_id attribute updateable on
subnets.  To conform to the uniqueness guarantees provided by
subnetpools and address scopes, the subnet cidr will be checked across
the subnetpool prefix list and across the entire address scope (if
applicable) to ensure the cidr has not already been allocated from
either the subnetpool or the address scope.

Adoption of a subnet by a subnetpool would have the following behavior:

1. If the subnet cidr has been configured in the address scope as a pool
prefix in a different subnetpool than the specified subnetpool, the
adoption into the specified subnetpool will be blocked

2. If the subnet cidr has been configured in the specified subnetpool as
a pool prefix and the pool prefix has not been allocated, the
subnetpool_id of the subnet will be updated and the cidr will be seen by
the subnetpool as allocated.

3. If the subnet cidr has been configured in the specified subnetpool as
a pool prefix  and the pool prefix has been allocated, adoption into the
specified subnet will be blocked.

4. If the subnet cidr has not been configured as a pool prefix in the
specified subnetpool and the pool prefix is not configured as a pool
prefix in any other subnetpools in the address scope, the cidr will be
added as a pool prefix to the specified subnetpool and marked as
allocated

5. If a subnet allocated from a subnetpool has its subnetpool_id
updated, the cidr is released back to the subnetpool upon completion of
the update.  Moving a subnet between subnetpools is subject to the same
restrictions as explained above.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: l3-ipam-dhcp rfe

** Tags added: rfe

** Tags added: l3-ipam-dhcp

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

Title:
  Enable adoption of an existing subnet into a subnetpool

Status in neutron:
  New

Bug description:
  It is currently not possible to take an existing subnet and move it
  into a subnetpool or address scope.  The subnetpool_id attribute on
  subnets is not updateable, meaning that once a subnet is created it
  cannot be moved between subnetpools or address scopes.  If a subnet
  was created without a subnetpool_id, it still cannot be moved into a
  subnetpool or address scope.  This is a barrier to the adoption
  features like subnetpools, address scopes, and BGP.  Many users likely
  have existing subnets that they would prefer to not destroy and re-
  create just for the purpose of being able to use these features.

  This RFE proposes making the subnetpool_id attribute updateable on
  subnets.  To conform to the uniqueness guarantees provided by
  subnetpools and address scopes, the subnet cidr will be checked across
  the subnetpool prefix list and across the entire address scope (if
  applicable) to ensure the cidr has not already been allocated from
  either the subnetpool or the address scope.

  Adoption of a subnet by a subnetpool would have the following
  behavior:

  1. If the subnet cidr has been configured in the address scope as a
  pool prefix in a different subnetpool than the specified subnetpool,
  the adoption into the specified subnetpool will be blocked

  2. If the subnet cidr has been configured in the specified subnetpool
  as a pool prefix and the pool prefix has not been allocated, the
  subnetpool_id of the subnet will be updated and the cidr will be seen
  by the subnetpool as allocated.

  3. If the subnet cidr has been configured in the specified subnetpool
  as a pool prefix  and the pool prefix has been allocated, adoption
  into the specified subnet will be blocked.

  4. If the subnet cidr has not been configured as a pool prefix in the
  specified subnetpool and the pool prefix is not configured as a pool
  prefix in any other subnetpools in the address scope, the cidr will be
  added as a pool prefix to the specified subnetpool and marked as
  allocated

  5. If a subnet allocated from a subnetpool has its subnetpool_id
  updated, the cidr is released back to the subnetpool upon completion
  of the update.  Moving a subnet between subnetpools is subject to the
  same restrictions as explained above.

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