← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1457986] Re: RFE: Need API to provide network IP allocation counts

 

Reviewed:  https://review.openstack.org/212955
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2f741ca5f9545c388270ddab774e9e030b006d8a
Submitter: Jenkins
Branch:    master

commit 2f741ca5f9545c388270ddab774e9e030b006d8a
Author: Mike Dorman <mdorman@xxxxxxxxxxx>
Date:   Thu Aug 13 21:24:58 2015 -0600

    Add API extension for reporting IP availability usage statistics
    
    Implements an API extension for reporting availibility of IP
    addresses on Neutron networks/subnets based on the blueprint
    proposed at https://review.openstack.org/#/c/180803/
    
    This provides an easy way for operators to count the number of
    used and total IP addresses on any or all networks and/or
    subnets.
    
    Co-Authored-By: David Bingham <dbingham@xxxxxxxxxxx>
    Co-Authored-By: Craig Jellick <craig.jellick@xxxxxxxxx>
    
    APIImpact
    DocImpact: As a new API, will need all new docs. See devref for details.
    
    Implements: blueprint network-ip-usage-api
    Closes-Bug: 1457986
    Change-Id: I81406054d46b2c0e0ffcd56e898e329f943ba46f


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
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 allocation counts

Status in neutron:
  Fix Released

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/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)

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


References