yahoo-eng-team team mailing list archive

[Carl Baldwin <carl@xxxxxxxxxxxxx>]

After some review and reading Neil's final comments, I'm going to close
this.  I'm about to crack IPAM for routed networks.  With this request
in mind, I'll be looking to evolve the IPAM interface so that it can
take host information into consideration.  I'll also be working on the
deferred IP allocation.

I think there will be a way to do all of this which can accommodate both
hard and soft boundaries for cidrs.  I'll have some code up for review
soon and will add Neil and Petra to the review.

In the meantime, I suggest we review and merge Petra's devref
contribution: [1].

[1] https://review.openstack.org/#/c/289460/

** Changed in: neutron
       Status: Triaged => Won't Fix

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

Title:
  [RFE] Host Aware IPAM

Status in neutron:
  Won't Fix

Bug description:
  In some Neutron use cases it is desirable for the IP address(es) that
  Neutron allocates to a VM to depend on the compute host that Nova
  chooses for that VM. For example, in the networking-calico approach
  where data is routed between compute hosts, it's desirable for the IP
  addresses that are used on a given host (or rack) to be clustered
  within a small IP prefix, so that the routes to those IP addresses can
  be aggregated on routers within the data center fabric. Neutron's new
  pluggable IPAM facility allows us in principle to start doing this,
  but we will need to design and implement three other pieces of the
  solution:

  - Firstly, we need a way for the pluggable IPAM framework to pass the
  chosen host into a pluggable IPAM module, such that a module can take
  the host into account if it so wishes.  (If this does not already
  exist - we are not yet sure!)

  - Secondly, to demonstrate that, we need a sample pluggable IPAM module that allocates IP addresses in some host-aware way.
  - Thirdly, we eventually need to enhance the port setup exchange between Nova and Neutron, such that Neutron can choose an IP address _after_ Nova has chosen the compute host.

  This work is being done as part of an Outreachy internship, and the
  last point cannot reasonably fit in that scope.  Hence this RFE
  proposes just the first two points, as a useful and concrete step
  towards the eventual complete picture.

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