<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><br>agree to use bug to fix it after the quota-per-tenant gets in. Although the quota-per-tenant is an extension, the quota framework in core can use quantum.conf to do the basic quota features.<span><br><br></span><br><br><font color="#990099">-----Salvatore Orlando <a class="moz-txt-link-rfc2396E" href="mailto:sorlando@nicira.com"><sorlando@nicira.com></a> wrote: -----</font><div style="padding-left: 5px;"><div style="padding-right: 0px; padding-left: 5px; border-left: 2px solid black;">To: <a class="moz-txt-link-abbreviated" href="mailto:gkotton@redhat.com">gkotton@redhat.com</a>, OpenStack Development Mailing List <a class="moz-txt-link-rfc2396E" href="mailto:openstack-dev@lists.openstack.org"><openstack-dev@lists.openstack.org></a><br>From: Salvatore Orlando <a class="moz-txt-link-rfc2396E" href="mailto:sorlando@nicira.com"><sorlando@nicira.com></a><br>Date: 08/14/2012 10:13PM<br>Subject: Re: [openstack-dev] [Quantum] Quotas vs. max_subnet_host_routes and max_dns_nameservers<br><br>Gary, <div><br></div><div>I agree with you.</div><div>The issue started in the patch for host_routes in subnet. I believe Simon did not find very easy to integrate with the Quota mechanism. </div><div>It would be great if Nachi could fix this in his patch both for port and subnet routes, otherwise we'll file a bug for it (assuming it's not already been filed).</div>
<div><br></div><div>Salvatore</div><div><br><div class="gmail_quote">On 14 August 2012 15:40, Gary Kotton <span dir="ltr"><<a href="mailto:gkotton@redhat.com" target="_blank">gkotton@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi,<br>
In the patch <a href="https://review.openstack.org/#/c/10791/" target="_blank">https://review.openstack.org/#<u></u>/c/10791/</a> two new configuration fields were introduced, namely max_dns_nameservers and max_subnet_host_routes. I am not sure if this is the correct thing to do. I think that the fact that now that we have Quota enforcement this should be treated there. It is more robust and when using the database plugin this can be treated per tenant (<a href="https://review.openstack.org/#/c/10484/" target="_blank">https://review.openstack.org/<u></u>#/c/10484/</a>).<br>
Any thoughts?<br>
Thanks<br>
Gary<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</blockquote></div><br></div>
<div><font face="Courier New,Courier,monospace" size="2">_______________________________________________<br>OpenStack-dev mailing list<br><a class="moz-txt-link-abbreviated" 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">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br></font></div></div></div></font>