yahoo-eng-team team mailing list archive

[OpenStack Infra <1457986@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/180803
Committed: https://git.openstack.org/cgit/openstack/neutron-specs/commit/?id=8a8a48216da5fe9c92cf6071a964964f9ef89fbd
Submitter: Jenkins
Branch:    master

commit 8a8a48216da5fe9c92cf6071a964964f9ef89fbd
Author: dbingham <dbingham@xxxxxxxxxxx>
Date:   Mon Nov 30 18:54:14 2015 -0700

    Network IP Availability Extension API
    
    Add a new network IP availability API Extension for operators to predict
    and react when networks are reaching IP capacity.
    
    ip availability api extension rfe
    
    APIImpact
    DocImpact
    
    Change-Id: Ifd42982aea5bbfc095e30bd2a221ec472d55519a
    Implements: blueprint network-ip-usage-api
    Closes-Bug: 1457986


** 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