Open Stack

 Hi, Neutrons,
We have desire to have an API for neutron to return ip-margin, or the number of IP still available for use, for each network belong to a tenant.
I have filed a launchpad issue 1503462. This is now marked as duplicate of 1457986.
I am glad to see there are more parties that are interested in this feature. I would like to see how we can coordinate the effort on this feature.We have two use-cases for this feature:
1. To assist nova to select a network when creating a new VM instance.    For this use-case, we like to have a tenant-id in GET request and get ip-margins for all the networks belong to the network.2. To provide information to monitor tools to show the capacities on dash-board. 
 For this use-case, we need to return network name in the response.We also have the implementation and accompanying tempest test scripts.The issue 1457986 is currently assigned to Mike Dorman. I am curious to see where we are on this issue. Is the draft REST API ready? Can we incorporate my use-case input into the considerations.
-- Aihua
Reference:1. https://bugs.launchpad.net/neutron/+bug/15034622. https://bugs.launchpad.net/neutron/+bug/1457986


Reply, Reply All or Forward | Moreopenstack-dev-owner at lists.openstack.org Toaihuaedwardli at yahoo.com Oct 8 at 11:41 AM----- Forwarded Message -----

You have to be a subscriber to post to this mailing list, so your
message has been automatically rejected. You can subscribe at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

If you think that your messages are being rejected in error, contact
the mailing list owner at %(listowner)


Hi, Neutrons,
We have desire to have an API for neutron to return ip-margin, or the number of IP still available for use, for each network belong to a tenant.
I have filed a launchpad issue 1503462. This is now marked as duplicate of 1457986.
I am glad to see there are more parties that are interested in this feature. I would like to see how we can coordinate the effort on this feature.We have two use-cases for this feature:
1. To assist nova to select a network when creating a new VM instance.    For this use-case, we like to have a tenant-id in GET request and get ip-margins for all the networks belong to the network.2. To provide information to monitor tools to show the capacities on dash-board. 
 For this use-case, we need to return network name in the response.We also have the implementation and accompanying tempest test scripts.The issue 1457986 is currently assigned to Mike Dorman. I am curious to see where we are on this issue. Is the draft REST API ready? Can we incorporate my use-case input into the considerations.
-- Aihua
Reference:1. https://bugs.launchpad.net/neutron/+bug/15034622. https://bugs.launchpad.net/neutron/+bug/1457986

== Aihua Edward Li ==
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151009/08106e7c/attachment.html>