Show available IP addresses #212

@jeremystretch commented on GitHub (Jul 18, 2016):

I think I'd prefer to just state the range, since unlike prefix aggregates IP addresses are atomic units. Generating aggregates to cover the space takes up more room on the page and can also make it more difficult to determine how much free space there is.

@jeremystretch commented on GitHub (Jul 18, 2016): I think I'd prefer to just state the range, since unlike prefix aggregates IP addresses are atomic units. Generating aggregates to cover the space takes up more room on the page and can also make it more difficult to determine how much free space there is.

adam commented

@kenspi commented on GitHub (Jul 19, 2016):

So maybe between, say, .42 and .50, we'd inject a row reading "7 IPs available?"

I think this is a reasonable solution and reduces clutter.

@kenspi commented on GitHub (Jul 19, 2016): > So maybe between, say, .42 and .50, we'd inject a row reading "7 IPs available?" I think this is a reasonable solution and reduces clutter.

adam commented

@malaiam commented on GitHub (Jul 27, 2016):

I would also like to have this feature. And I agree with @jeremystretch 's range proposal, it will work both on IPv4 and IPv6. And this should be showed in a slightly different colour, light green or similar.

I also think this feature should be extended to VLANs within the group to show available VLANs as ranges. (btw, I belive the sites with no VLAN group should have an implicit default group, even if the user is not creating one).

Otherwise great work with the project Jeremy, I think it really is adding features other IPAMs don't have, even though a few more features could be welcomed.

@malaiam commented on GitHub (Jul 27, 2016): I would also like to have this feature. And I agree with @jeremystretch 's range proposal, it will work both on IPv4 and IPv6. And this should be showed in a slightly different colour, light green or similar. I also think this feature should be extended to VLANs within the group to show available VLANs as ranges. (btw, I belive the sites with no VLAN group should have an implicit default group, even if the user is not creating one). Otherwise great work with the project Jeremy, I think it really is adding features other IPAMs don't have, even though a few more features could be welcomed.

adam commented

@alexjhart commented on GitHub (Jul 28, 2016):

phpipam might be a source of inspiration. I think they do a great job with IPAM in general. Seems like netbox does a better job with DCIM and phpipam does a better job with IPAM, while they each try to cover both needs. It will be interesting to see where the two projects end up long term.

@alexjhart commented on GitHub (Jul 28, 2016): [phpipam](https://github.com/phpipam/phpipam) might be a source of [inspiration](http://demo.phpipam.net/subnets/1/33/). I think they do a great job with IPAM in general. Seems like netbox does a better job with DCIM and phpipam does a better job with IPAM, while they each try to cover both needs. It will be interesting to see where the two projects end up long term.

adam commented

@anthraxau commented on GitHub (Aug 2, 2016):

Agreed, phpipam does handle that very well.

@anthraxau commented on GitHub (Aug 2, 2016): Agreed, phpipam does handle that very well.

adam commented

@jeremystretch commented on GitHub (Aug 2, 2016):

@alexjhart @anthraxau Could you elaborate on what you like about phpIPAM's view?

IMO this is a confusing way to show IP addresses. Why does the free range appear in the hostname column? I was thinking of something like this, but more similar to how we show unallocated child prefixes.

The block display, while visually appealing with small IPv4 networks, isn't very useful for prefixes larger than a /24 (and not at all with IPv6).

@jeremystretch commented on GitHub (Aug 2, 2016): @alexjhart @anthraxau Could you elaborate on what you like about phpIPAM's view? ![phpipam1](https://cloud.githubusercontent.com/assets/13487278/17333982/95f30f70-58a2-11e6-8474-04bd4043641d.png) IMO this is a confusing way to show IP addresses. Why does the free range appear in the hostname column? I was thinking of something like this, but more similar to how we show unallocated child prefixes. ![phpipam2](https://cloud.githubusercontent.com/assets/13487278/17334072/e183f5a8-58a2-11e6-83dc-61cf02dc93fb.png) The block display, while visually appealing with small IPv4 networks, isn't very useful for prefixes larger than a /24 (and not at all with IPv6).

adam commented

@anthraxau commented on GitHub (Aug 2, 2016):

In the regards to the first image I just like how the dhcp range is grouped. You're right other than that it behaves incorrectly.

The 2nd image is nice to see what's available at a quick glance but I agree that on a /22 or larger it would be painful I didn't even think of IPv6 :(

I've been using excel for a /22 and a few other prefixes so I'm feeling abit blessed with what you have currently.

I'm not sure if other people do this but I tend to group similar devices in groups on the prefix for example routers .250-254 core switches .240-249 VMware stuff .100-.149 etc and I usually colour code them for easy navigation of my spreadsheet so that I can quickly glance other it and see any gaps that are available. I've noticed you do this for rack devices. Would be nice to be able to enable this for the ipam

@anthraxau commented on GitHub (Aug 2, 2016): In the regards to the first image I just like how the dhcp range is grouped. You're right other than that it behaves incorrectly. The 2nd image is nice to see what's available at a quick glance but I agree that on a /22 or larger it would be painful I didn't even think of IPv6 :( I've been using excel for a /22 and a few other prefixes so I'm feeling abit blessed with what you have currently. I'm not sure if other people do this but I tend to group similar devices in groups on the prefix for example routers .250-254 core switches .240-249 VMware stuff .100-.149 etc and I usually colour code them for easy navigation of my spreadsheet so that I can quickly glance other it and see any gaps that are available. I've noticed you do this for rack devices. Would be nice to be able to enable this for the ipam

adam commented

@alexjhart commented on GitHub (Aug 2, 2016):

I never considered the ranges to be under the hostname column. My eye accepted that as a range of available IPs and find the offset helpful in establishing the difference. More important than which column data shows up under is the display and grouping of unused space. Having a place holder with a different row color and a range displayed of the available space is adequate. I also like similar types of ranges being grouped, like the dhcp range shown here, though that is less important to me than showing available space. It just plays into the argument you had for the next screenshot where doing things that help with large subnets is important. This could streamline the display of a lot of larger subnets.

I could care less about this visual display and agree it isn't practical for larger subnets. If you did want to have something like this, maybe you would set a limit for max prefix size it is displayed for.

I think you can take a similar approach to what you do with the child prefixes table. Here you have available subnets (though I didn't realize this at first, so maybe consider a different row color). Those are hyperlinked to a create new subnet form with the range autofilled, which I like. Though the workflow might be nicer if you used a popup rather than directing the user to a new page?

Anyway, maybe something like this. I imagine that range there is hyperlinked and takes you to a new IP address form for the first IP in that range. By the way, it would be nice to be able to add a range of IPs, not just one at a time. Again, I think it would flow better if you handle the addition in a popup (similar to phpipam).

I like @anthraxau's idea of having color coded ranges. Maybe this can be accomplished with a tag #132 I imagine something similar to gmail labels where you have have multiple tags shown in the table which can have colors assigned to them, to make different things stand out more. That idea is also off topic though.

@alexjhart commented on GitHub (Aug 2, 2016): ![image](https://cloud.githubusercontent.com/assets/216209/17337880/86795616-5899-11e6-8e7b-1dc8dc1f7bf9.png) I never considered the ranges to be under the hostname column. My eye accepted that as a range of available IPs and find the offset helpful in establishing the difference. More important than which column data shows up under is the display and grouping of unused space. Having a place holder with a different row color and a range displayed of the available space is adequate. I also like similar types of ranges being grouped, like the dhcp range shown here, though that is less important to me than showing available space. It just plays into the argument you had for the next screenshot where doing things that help with large subnets is important. This could streamline the display of a lot of larger subnets. ![image](https://cloud.githubusercontent.com/assets/216209/17338057/84ff0960-589a-11e6-8e77-229d7290e94c.png) I could care less about this visual display and agree it isn't practical for larger subnets. If you did want to have something like this, maybe you would set a limit for max prefix size it is displayed for. ![image](https://cloud.githubusercontent.com/assets/216209/17338926/66076ed6-589e-11e6-9001-d6121d80bcd0.png) I think you can take a similar approach to what you do with the child prefixes table. Here you have available subnets (though I didn't realize this at first, so maybe consider a different row color). Those are hyperlinked to a create new subnet form with the range autofilled, which I like. Though the workflow might be nicer if you used a popup rather than directing the user to a new page? ![image](https://cloud.githubusercontent.com/assets/216209/17338870/1959b5c6-589e-11e6-8146-d2032178ff59.png) Anyway, maybe something like this. I imagine that range there is hyperlinked and takes you to a new IP address form for the first IP in that range. By the way, it would be nice to be able to add a range of IPs, not just one at a time. Again, I think it would flow better if you handle the addition in a popup (similar to phpipam). I like @anthraxau's idea of having color coded ranges. Maybe this can be accomplished with a tag #132 I imagine something similar to gmail labels where you have have multiple tags shown in the table which can have colors assigned to them, to make different things stand out more. That idea is also off topic though.

adam commented

@jeremystretch commented on GitHub (Aug 3, 2016):

How about this?

Clicking one of the "free IPs" buttons takes the user to the IP adress creation form, pre-populated with the first available IP in that range.

@jeremystretch commented on GitHub (Aug 3, 2016): How about this? ![netbox_ip_rows](https://cloud.githubusercontent.com/assets/13487278/17369606/fb21969a-5966-11e6-9003-7115f435c3ce.png) Clicking one of the "free IPs" buttons takes the user to the IP adress creation form, pre-populated with the first available IP in that range.

adam commented

@ambique commented on GitHub (Aug 3, 2016):

Great.

On Wednesday, 3 August 2016, Jeremy Stretch notifications@github.com
wrote:

How about this?

[image: netbox_ip_rows]
https://cloud.githubusercontent.com/assets/13487278/17369606/fb21969a-5966-11e6-9003-7115f435c3ce.png

Clicking one of the "free IPs" buttons takes the user to the IP adress
creation form, pre-populated with the first available IP in that range.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/digitalocean/netbox/issues/289#issuecomment-237257185,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANLscxU8TJb4f073j-4UQ9OREj8zTEwoks5qcLTugaJpZM4JL12t
.

Arafat M. Bique
Security Analyst

Esta mensagem foi enviada a partir de um dispositivo móvel, pelo que poderá
conter erros de acentuação e informação incompleta.

This message was sent from a mobile device so some features and information
might not be completed or available.

@ambique commented on GitHub (Aug 3, 2016): Great. On Wednesday, 3 August 2016, Jeremy Stretch notifications@github.com wrote: > How about this? > > [image: netbox_ip_rows] > https://cloud.githubusercontent.com/assets/13487278/17369606/fb21969a-5966-11e6-9003-7115f435c3ce.png > > Clicking one of the "free IPs" buttons takes the user to the IP adress > creation form, pre-populated with the first available IP in that range. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > https://github.com/digitalocean/netbox/issues/289#issuecomment-237257185, > or mute the thread > https://github.com/notifications/unsubscribe-auth/ANLscxU8TJb4f073j-4UQ9OREj8zTEwoks5qcLTugaJpZM4JL12t > . ## --- Arafat M. Bique Security Analyst CISA | GCFE | GWAPT | GPEN | CISSP | CHFI | CEH | CCNP | CCNA SECURITY | CCAI | MCSE Esta mensagem foi enviada a partir de um dispositivo móvel, pelo que poderá conter erros de acentuação e informação incompleta. This message was sent from a mobile device so some features and information might not be completed or available.

adam commented

@alexjhart commented on GitHub (Aug 3, 2016):

Looks good. Only improvement I can see would be to add the ranges like I had in my mockup.

@alexjhart commented on GitHub (Aug 3, 2016): Looks good. Only improvement I can see would be to add the ranges like I had in my mockup.

adam commented

@bellwood commented on GitHub (Aug 3, 2016):

Being able to "add an IP" from the free block would be great

@bellwood commented on GitHub (Aug 3, 2016): Being able to "add an IP" from the free block would be great

adam commented

@jeremystretch commented on GitHub (Aug 3, 2016):

@bellwood The "free IPs" button is indeed a link to add an IP, initialized to the first available IP in the range.

@jeremystretch commented on GitHub (Aug 3, 2016): @bellwood The "free IPs" button is indeed a link to add an IP, initialized to the first available IP in the range.

adam commented