<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 12 Feb 2017, at 12:13, Boris Bobrov <<a href="mailto:bbobrov@mirantis.com" class="">bbobrov@mirantis.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div class="">I would like to talk about it too.<br class="">
<br class="">
On 02/10/2017 11:56 PM, Matt Riedemann wrote:<br class="">
<blockquote type="cite" class="">Operators want hierarchical quotas [1]. Nova doesn't have them yet and<br class="">
we've been hesitant to invest scarce developer resources in them since<br class="">
we've heard that the implementation for hierarchical quotas in Cinder<br class="">
has some issues. But it's unclear to some (at least me) what those<br class="">
issues are.<br class="">
</blockquote>
<br class="">
I don't know what the actual issue is, but from from keystone POV<br class="">
the issue is that it basically replicates project tree that is stored<br class="">
in keystone. On top of usual replication issues, there is another one --<br class="">
it requires too many permissions. Basically, it requires service user<br class="">
to be cloud admin.<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>I have not closely followed the cinder implementation since the CERN and BARC Mumbai focus has more around Nova.</div>
<div><br class="">
</div>
The various feedbacks I have had was regarding how to handle overcommit on the cinder proposal. A significant share of the operator community would like to allow</div>
<div><br class="">
</div>
<div>- No overcommit for the ‘top level’ project (i.e. you can’t use more than you are allocated)]</div>
<div>- Sub project over commit is OK (i.e. promising your sub projects more is OK, sum of the commitment to subprojects>project is OK but should be given an error if it actually happens)</div>
<div><br class="">
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">
<div class=""><br class="">
<blockquote type="cite" class="">Has anyone already planned on talking about hierarchical quotas at the<br class="">
PTG, like the architecture work group?<br class="">
<br class="">
I know there was a bunch of razzle dazzle before the Austin summit about<br class="">
quotas, but I have no idea what any of that led to. Is there still a<br class="">
group working on that and can provide some guidance here?<br class="">
</blockquote>
<br class="">
In my opinion, projects should not re-implements quotas every time.<br class="">
I would like to have a common library for enforcing quotas (usages)<br class="">
and a service for storing quotas (limits). We should also think of a<br class="">
way to transfer necessary projects subtree from keystone to quota<br class="">
enforcer.<br class="">
<br class="">
We could store quota limits in keystone and distribute it in token<br class="">
body, for example. Here is a POC that we did some time ago --<br class="">
<a href="https://review.openstack.org/#/c/403588/" class="">https://review.openstack.org/#/c/403588/</a> and<br class="">
<a href="https://review.openstack.org/#/c/391072/" class="">https://review.openstack.org/#/c/391072/</a><br class="">
But it still has the issue with permissions.<br class="">
<br class="">
</div>
</div>
</blockquote>
<div><br class="">
</div>
There has been an extended discussion since the Boson proposal at the Hong Kong summit on how to handle quotas, where a full quota service was proposed.</div>
<div><br class="">
</div>
<div>A number of ideas have emerged since then</div>
<div><br class="">
</div>
<div>- Quota limits stored in Keystone with the project data</div>
<div>- An oslo library to support checking that a resource request would be OK</div>
<div><br class="">
</div>
<div>One Forum session at the summit is due to be on this topic. </div>
<div><br class="">
</div>
<div>Some of the academic use cases are described in <a href="https://openstack-in-production.blogspot.fr/2016/04/resource-management-at-cern.html" class="">https://openstack-in-production.blogspot.fr/2016/04/resource-management-at-cern.html</a> but commercial
reseller models are valid here where</div>
<div><br class="">
</div>
<div>- company A has valuable resources to re-sell (e.g. flood risk and associated models)</div>
<div>- company B signs an agreement with Company A (e.g. an insurance company wants to use flood risk data as factor in their cost models)</div>
<div><br class="">
</div>
<div>The natural way of delivering this is that ‘A’ gives a pricing model based on ‘B’’s consumption of compute and storage resources.</div>
<div><br class="">
</div>
<div>Tim</div>
<div><br class="">
</div>
<div><br class="">
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">
<div class="">
<blockquote type="cite" class="">[1]<br class="">
<a href="http://lists.openstack.org/pipermail/openstack-operators/2017-January/012450.html" class="">http://lists.openstack.org/pipermail/openstack-operators/2017-January/012450.html</a><br class="">
<br class="">
<br class="">
</blockquote>
<br class="">
__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">
OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</body>
</html>