<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 23, 2014 at 4:07 PM, Florent Flament <span dir="ltr"><<a href="mailto:florent.flament-ext@cloudwatt.com" target="_blank">florent.flament-ext@cloudwatt.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I understand that not everyone may be interested in such feature.<br>
<br>
On the other hand, some (maybe shallow) Openstack users may be<br>
interested in setting quotas on users or projects. Also, this feature<br>
wouldn't do any harm to the other users who wouldn't use it.<br></blockquote><div><br></div><div>The "harm" comes in the form of time spent in code review, documentation, testing/infra, long term maintenance, summit bandwidth, vulnerability management, etc, leveraged upon the rest of the community.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
If some contributors are willing to spend some time in adding this<br>
feature to Openstack, is there any reason not to accept it ?<br>
<div class="im"><br>
On Thu, 2014-01-23 at 14:55 -0600, Dolph Mathews wrote:<br>
><br>
> On Thu, Jan 23, 2014 at 9:59 AM, Florent Flament<br>
> <<a href="mailto:florent.flament-ext@cloudwatt.com">florent.flament-ext@cloudwatt.com</a>> wrote:<br>
> Hi,<br>
><br>
><br>
> Although it is true that projects and users don't consume a<br>
> lot of resources, I think that there may be cases where<br>
> setting quotas (possibly large) may be useful.<br>
><br>
><br>
><br>
> For instance, a cloud provider may wish to prevent domain<br>
> administrators to mistakingly create an infinite number of<br>
> users and/or projects, by calling APIs in a bugging loop.<br>
><br>
><br>
><br>
> That sounds like it would be better solved by API rate limiting, not<br>
> quotas.<br>
><br>
><br>
><br>
><br>
> Moreover, if quotas can be disabled, I don't see any reason<br>
> not to allow cloud operators to set quotas on users and/or<br>
> projects if they wishes to do so for whatever marketing reason<br>
> (e.g. charging more to allow more users or projects).<br>
><br>
><br>
><br>
> That's the shallow business decision I was alluding to, which I don't<br>
> think we have any reason to support in-tree.<br>
><br>
><br>
><br>
><br>
> Regards,<br>
><br>
> Florent Flament<br>
><br>
><br>
><br>
><br>
><br>
</div>> ______________________________________________________________<br>
<div class=""><div class="h5">> From: "Dolph Mathews" <<a href="mailto:dolph.mathews@gmail.com">dolph.mathews@gmail.com</a>><br>
> To: "OpenStack Development Mailing List (not for usage<br>
> questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
> Sent: Thursday, January 23, 2014 3:09:51 PM<br>
> Subject: Re: [openstack-dev] [Keystone] bp proposal: quotas on<br>
> users and projects per domain<br>
><br>
><br>
><br>
> ... why? It strikes me as a rather shallow business decision<br>
> to limit the number of users or projects in a system, as<br>
> neither are actually cost-consuming resources.<br>
><br>
><br>
> On Thu, Jan 23, 2014 at 6:43 AM, Matthieu Huin<br>
> <<a href="mailto:matthieu.huin@enovance.com">matthieu.huin@enovance.com</a>> wrote:<br>
> Hello,<br>
><br>
> I'd be interested in opinions and feedback on the<br>
> following blueprint:<br>
> <a href="https://blueprints.launchpad.net/keystone/+spec/tenants-users-quotas" target="_blank">https://blueprints.launchpad.net/keystone/+spec/tenants-users-quotas</a><br>
><br>
> The idea is to add a mechanism preventing the creation<br>
> of users or projects once a quota per domain is met. I<br>
> believe this could be interesting for cloud providers<br>
> who delegate administrative rights under domains to<br>
> their customers.<br>
><br>
> I'd like to hear the community's thoughts on this,<br>
> especially in terms of viability.<br>
><br>
> Many thanks,<br>
><br>
> Matthieu Huin<br>
><br>
> <a href="mailto:mhu@enovance.com">mhu@enovance.com</a><br>
> <a href="http://www.enovance.com" target="_blank">http://www.enovance.com</a><br>
> eNovance SaS - 10 rue de la Victoire 75009 Paris -<br>
> France<br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>