[openstack-dev] [Neutron] Update on "DB" IPAM driver

Carl Baldwin carl at ecbaldwin.net
Sat Feb 14 21:51:34 UTC 2015


On Feb 13, 2015 5:54 AM, "Salvatore Orlando" <sorlando at nicira.com> wrote:

> - Considering an alternative to availability ranges. Pre-generation of IP
entries is unpractical (think IPv6), so that's not an option.
Unfortunately, I have not yet explored in detail this route.

The availability range stuff is hard.  I was talking about it with Ryan
Tidwell last week.  I actually wonder if it would be much worse to just
load all of the allocations and compute availability on demand.  It seems
drastic and probably isn't better but that is how bad storing and
maintaining availability is in the db.

I suspect it will be more difficult for subnet allocation.

Would you consider an alternative that pregenerated up to N entries and
kept a flag on allocations stating whether they are in use or can be
recycled?

Carl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150214/f25601ad/attachment.html>


More information about the OpenStack-dev mailing list