Open Stack

On Wed, Jun 29, 2016 at 12:43 PM, Joseph Bajin <josephbajin at gmail.com> wrote:
> Hi there,
>
> It looks like QOS is already available within the Mitaka release.   Maybe it
> doesn't have all the features you need, but looks to be a good start.
> http://docs.openstack.org/mitaka/networking-guide/adv-config-qos.html

It's available from Neutron's Liberty release even. The new feature
provides a new QoS bandwidth limitation API, which when using the OVS
agent, is implemented via an OVS feature as such [1].

It sets the 'ingress_policing_rate' and 'ingress_policing_burst'
attributes on the VM's interface record in the ovsdb. Internally to
OVS that is implemented via 'tc' and by dropping packets over the
specified rate as detailed here [2].

[1] https://github.com/openstack/neutron/blob/stable/liberty/neutron/agent/common/ovs_lib.py#L539
[2] http://openvswitch.org/support/config-cookbooks/qos-rate-limiting/

>
> I haven't used it yet, but maybe someone else will pipe up with some
> expierence.
>
> --Joe
>
> On Wed, Jun 29, 2016 at 12:36 PM, Daniel Levy <dlevy at us.ibm.com> wrote:
>>
>> Hi all,
>> I'd like to learn about potential solutions anyone out there is using for
>> bandwidth limitations on VMs. Potentially applying QOS (quality of service)
>> rules on the VM ports in an automated fashion.
>> If there are no current solutions, I might submit a blue print to tackle
>> this issue
>>
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>