Operators have requested an API that allows them to quickly and easily determine the IP capacity of a network or subnet. Rather than discovering a network is full, an api could be proactively called by an operator or monitor to give some measure of when a network is reaching its capacity.
Some things desired from a new API for both network and subnets
* used IPs - How many IPs are reserved from a network/subnet
* total IPs - The capacity of IPs for this network/subnet
* Enough information about the network/subnet to be able to fetch detailed information about the resource (possible examples: id, name)
Naturally used_ips/total_ips gives the user a way to determine the percentage the resource has been consumed.
Some references to those needing this API:
* Philidelphia operators at the OPs meetup expressed great interest after watching a presentation describing this use.
* GoDaddy in-house implementation: In use for 1+ years. Also called by in-house NetworkAwareFilterScheduler. GoDaddy implementation:https://github.com/godaddy/openstack-neutron/commit/fcf325f9f9f7a9f87ba6bc1c53f9212d0e2decee
* Rackspace implementation: https://github.com/rackerlabs/quark/blob/master/quark/ip_availability.py#L48
Some notes about related patches (added 2015-11-17):
* https://review.openstack.org/180803 (Neutron Spec)
* https://review.openstack.org/#/c/212955 (Neutron patch)
* https://review.openstack.org/#/c/234541 (Second Neutron patch)
Guidelines, details on how to write RFE's, and the process for handling features if you have already submitted specs in the past, but are yet to be complete. can be found here:
https:/ /github. com/openstack/ neutron/ blob/master/ doc/source/ policies/ blueprints. rst
For more details, please reach out on #openstack-neutron or openstack-dev ML [neutron].