Open Stack

Everyone should be able to comment on specs, as long as you have a launchpad account.  It would probably be more productive to post these comments there.

As far as extending the spec to include usage reporting on all resources:  while I don’t disagree with you that it would be good to have those other features, we are trying to not boil the ocean here.  We’re primarily operators, not OpenStack developers, and this is a bite small enough that we think we can chew (we actually have it implemented internally already.)  If there are other developer resources willing to take on the extra work, I’m all for it, but I feel like just getting this out there as a starting point is a more realistic goal.  I think the url structure proposed in the spec will make it easily extensible to more resource types later.

Mike


From: Daniel Comnea
Date: Wednesday, May 27, 2015 at 4:18 PM
To: Mike Dorman
Cc: OpenStack Operators
Subject: Re: [Openstack-operators] Spec for Neutron Network IP Usage Extension API

Hi Mike,

Unfortunately i don't have privilege to review any spec however will provide my view here since i just came around a need for this in IceHouse.

The basic problem this blueprint is trying to solve:

   **Need an API to determine network IP usage.**
[DC]: can the goal be extended to include more info about:

  *   report usage of all quotas from neutron side: FIPs, security groups, ports,network, pool, subnet, security_groups_rule

Use Case #1: Admin invokes API extension to get detailed information
    about network IP usage. From that data, admin can act on networks that are nearly full.

[DC]: the admin should be able to:

  *   find out the usage of the all above resources
  *   filter out per tenant_id
  *   differentiate how many say FIPs or VIPs were never been allocated and how many are reusable


Thanks,
Dani







On Thu, May 7, 2015 at 4:29 PM, Mike Dorman <mdorman at godaddy.com<mailto:mdorman at godaddy.com>> wrote:
Hi all,

For those of you who were interested in our network IP usage API
extensions from the PHL meet up, we have this spec in play for it.  Please
review and comment!

As a reminder, the raw code/patch for this is also available at
https://github.com/godaddy/openstack-neutron/tree/network-ip-usage and
https://github.com/godaddy/openstack-neutron/commit/fcf325f9f9f7a9f87ba6bc1
c53f9212d0e2decee

I’ll briefly review this stuff during arch show and tell at the summit, so
happy to discuss more at that time as well.  Thanks!

Thanks,
Mike





On 5/6/15, 6:34 PM, "David Bingham (Code Review)" <review at openstack.org<mailto:review at openstack.org>>
wrote:

>David Bingham has uploaded a new change for review.
>
>  https://review.openstack.org/180803
>
>Change subject: Propose Network IP Usage Extension API for Liberty
>......................................................................
>
>Propose Network IP Usage Extension API for Liberty
>
>Propose adding a simple new Network IP Usage API Extension for
>operators to predict and react when networks reaching capacity.
>
>Change-Id: Ifd42982aea5bbfc095e30bd2a221ec472d55519a
>---
>A specs/liberty/network-ip-usage-api.rst
>1 file changed, 542 insertions(+), 0 deletions(-)
>
>
>  git pull ssh://review.openstack.org:29418/openstack/neutron-specs<http://review.openstack.org:29418/openstack/neutron-specs>
>refs/changes/03/180803/1
>--
>To view, visit https://review.openstack.org/180803
>To unsubscribe, visit https://review.openstack.org/settings
>
>Gerrit-MessageType: newchange
>Gerrit-Change-Id: Ifd42982aea5bbfc095e30bd2a221ec472d55519a
>Gerrit-PatchSet: 1
>Gerrit-Project: openstack/neutron-specs
>Gerrit-Branch: master
>Gerrit-Owner: David Bingham <dbingham at godaddy.com<mailto:dbingham at godaddy.com>>
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150529/3a03a97e/attachment-0001.html>