[openstack-dev] [Neutron][QoS] Applying QoS as Quota

Veiga, Anthony Anthony_Veiga at cable.comcast.com
Wed Sep 10 13:10:43 UTC 2014



Using the quota system would be a nice option to have.

Can you clarify what you mean by cumulative bandwidth for the tenant? It would be possible to rate limit at the tenant router, but having a cumulative limit enforced inside of a tenant would be difficult.

On Wed, Sep 10, 2014 at 1:03 AM, Giuseppe Cossu <giuseppe.cossu at create-net.org<mailto:giuseppe.cossu at create-net.org>> wrote:

Hello everyone,

Looking at the QoS blueprint (proposed for incubation), I suggest to consider adding some parameters to Neutron Quotas. Let’s suppose using rate-limit for managing QoS. The quota parameters could be such as rate_limit (per port) and max_bandwidth (per tenant). In this way it is possible to set/manage QoS quotas from the admin side, and for instance set the maximum bandwidth allowed per tenant (cumulative).
What do you think about it?

I’m cautious about this.  We’d either need to allow a “Number of DSCP settings” and set them outside the quota or leave it out altogether.  Let’s not forget that there’s more than just rate limiting in QoS, and we need to make sure all the options are included.  Otherwise, there’s going to be a lot of user and operator confusion as to what is and isn’t considered part of the quota.
-Anthony

Regards,
Giuseppe

--------------------------------------------------------
Giuseppe Cossu
CREATE-NET
--------------------------------------------------------

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




--
Kevin Benton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140910/49956dc5/attachment.html>


More information about the OpenStack-dev mailing list