yahoo-eng-team team mailing list archive

[David Bingham <dbingham@xxxxxxxxxxx>]

Public bug reported:

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/7a20d2c2c7d5a01416c9d5122dd1586f7421bfa7
* Rackspace implementation: https://github.com/rackerlabs/quark/blob/master/quark/ip_availability.py#L48

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: api extension rfe usage

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

Title:
  RFE: Need API to provide network IP usage information

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  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/7a20d2c2c7d5a01416c9d5122dd1586f7421bfa7
  * Rackspace implementation: https://github.com/rackerlabs/quark/blob/master/quark/ip_availability.py#L48

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