Duncan,<br><br>Thank you for the suggestion, will do.<br><div class="gmail_quote"><div dir="ltr">On Wed, 23 Dec 2015 at 10:55, Duncan Thomas <<a href="mailto:duncan.thomas@gmail.com">duncan.thomas@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">On a cloud with a large number of tenants, this is going to involve a large number of API calls. I'd suggest you put a spec into cinder to add an API call for getting the totals straight out of the DB - it should be easy enough to add.<br></div><div class="gmail_extra"></div><div class="gmail_extra"><br><div class="gmail_quote">On 18 December 2015 at 20:35, Timur Sufiev <span dir="ltr"><<a href="mailto:tsufiev@mirantis.com" target="_blank">tsufiev@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Matt,<div><br></div><div>actually Ivan (Ivan, thanks a lot!) showed me the exact cinderclient call that I needed. Now I know how to retrieve Cinder quota usage info per-tenant, seems that to retrieve the same info cloud-wide I should sum up all the available tenant usages.</div><div><br></div><div>With Cinder quota usages being sorted out, my next goal is Nova and Neutron. As for Neutron, there are plenty of quota-related calls I'm going to play with next week, perhaps there is something suitable for my use case. But as for Nova, I haven't found something similar to 'usage' of cinderclient call, so help from someone familiar with Nova is very appreciated :).</div><div><br></div><div>[0] <a href="https://github.com/openstack/python-cinderclient/blob/master/cinderclient/v2/quotas.py#L36" target="_blank">https://github.com/openstack/python-cinderclient/blob/master/cinderclient/v2/quotas.py#L36</a></div></div><div><div><br><div class="gmail_quote"><div dir="ltr">On Fri, Dec 18, 2015 at 5:17 PM Matt Riedemann <<a href="mailto:mriedem@linux.vnet.ibm.com" target="_blank">mriedem@linux.vnet.ibm.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On 12/17/2015 2:40 PM, Ivan Kolodyazhny wrote:<br>
> Hi Timur,<br>
><br>
> Did you try this Cinder API [1]? Here [2] is cinderclient output.<br>
><br>
><br>
><br>
> [1]<br>
> <a href="https://github.com/openstack/python-cinderclient/blob/master/cinderclient/v2/quotas.py#L33" rel="noreferrer" target="_blank">https://github.com/openstack/python-cinderclient/blob/master/cinderclient/v2/quotas.py#L33</a><br>
> [2] <a href="http://paste.openstack.org/show/482225/" rel="noreferrer" target="_blank">http://paste.openstack.org/show/482225/</a><br>
><br>
> Regards,<br>
> Ivan Kolodyazhny,<br>
> <a href="http://blog.e0ne.info/" rel="noreferrer" target="_blank">http://blog.e0ne.info/</a><br>
><br>
> On Thu, Dec 17, 2015 at 8:41 PM, Timur Sufiev <<a href="mailto:tsufiev@mirantis.com" target="_blank">tsufiev@mirantis.com</a><br>
> <mailto:<a href="mailto:tsufiev@mirantis.com" target="_blank">tsufiev@mirantis.com</a>>> wrote:<br>
><br>
> Hello, folks!<br>
><br>
> I'd like to initiate a discussion of the feature request I'm going<br>
> to make on behalf of Horizon to every core OpenStack service which<br>
> supports Quota feature, namely Cinder, Nova and Neutron.<br>
><br>
> Although all three services' APIs support special calls to get<br>
> current quota limitations (Nova and Cinder allows to get and update<br>
> both per-tenant and default cloud-wide limitations, Neutron allows<br>
> to do it only for per-tenant limitations), there is no special call<br>
> in any of these services to get current per-tenant usage of quota.<br>
> Because of that Horizon needs to get, say for 'volumes' quota, a<br>
> list of Cinder volumes in the current tenant and then just calculate<br>
> its length [1]. When there are really a lot of entities in tenant -<br>
> instances/volumes/security groups/whatever - all this calls sum up<br>
> and make rendering pages in Horizon much more slower than it could<br>
> be. Is it possible to provide special API calls to alleviate this?<br>
><br>
> [1]<br>
> <a href="https://github.com/openstack/horizon/blob/9.0.0.0b1/openstack_dashboard/usage/quotas.py#L350" rel="noreferrer" target="_blank">https://github.com/openstack/horizon/blob/9.0.0.0b1/openstack_dashboard/usage/quotas.py#L350</a><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe:<br>
> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
I think Timur is asking for a way to filter on only certain resources<br>
for quota usage/limits, like volumes in cinder or instances in nova,<br>
rather than getting back all resource usage/limits per tenant.<br>
<br>
Is that correct, Timur?<br>
<br>
While it's possible to add this, I'm not sure how much time it's<br>
actually going to save in the DB query time to get the quota information<br>
for a tenant.<br>
<br>
Anyway, it's an API change so it would require a spec for nova which<br>
means we wouldn't be getting to that until at least N since we're in<br>
spec freeze for mitaka.<br>
<br>
--<br>
<br>
Thanks,<br>
<br>
Matt Riedemann<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>
</div></div><br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br><br clear="all"><br></div><div class="gmail_extra">-- <br><div><div dir="ltr"><div>-- <br>Duncan Thomas</div></div></div>
</div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>