IP block allocations

[GoogleCodeExporter]

Problem:

Feature request: IP block allocations, instead of all individual IP addressing.

From request email: "It would be convenient to me if I could search for
open address blocks (ie:  I need X boxes (drop down box), and it searches
in that subnet for that many continuous IP's that lay on an appropriately
sized network boundary)."

Fix:

Make it so! This would be easy to tie into issue #2 and would be easily
represented by listing a bunch of IP model objects and letting ranges be
chosen from there.

Additional information:

Definitely give priority to IP blocks that lie on a network boundary and
tell the user what the CIDR netmask is for that block.

Original issue reported on code.google.com by fotinaki...@gmail.com on 27 Jan 2009 at 10:50

[GoogleCodeExporter]

I don't know if this is a sustainable approach, since we tend to get a lot of
fragmentation in our networks.  Allowing people to add a CSV of hosts would 
make it
likely that the hosts are more or less contiguous when a network isn't highly
fragmented.  Consecutive IPs are overrated, though -- that is why we invented 
DNS, so
your IP doesn't matter.

There is code in ipm.py that will give a list of free IP addresses broken into 
the
largest possible CIDR blocks in a given network range that could help you in 
your quest:

openipam % show_addresses network 129.123.54.0/24
        129.123.54.37
        129.123.54.38
        129.123.54.49
        129.123.54.50/31
        129.123.54.52/30
        129.123.54.56/29
        129.123.54.64/26
        129.123.54.128
        129.123.54.151
        129.123.54.152/29
        129.123.54.160/27
        129.123.54.192/27
        129.123.54.224/28
        129.123.54.240/29
        129.123.54.248/30
        129.123.54.252/31

Original comment by ekoyle@gmail.com on 28 Jan 2009 at 7:42