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
I haven't used it yet, but maybe someone else will pipe up with some
e
We've been using this for some time now (since at least Kilo). We set them
per flavor not per instance.
https://wiki.openstack.org/wiki/InstanceResourceQuota
Bandwidth limits
Nova Extra Specs keys:
- vif_inbound_average
- vif_outbound_average
- vif_inbound_peak
- vif_outbound_peak
ay, June 29, 2016 at 10:43 AM
To: Daniel Levy mailto:dl...@us.ibm.com>>
Cc: OpenStack Operators
mailto:openstack-operators@lists.openstack.org>>
Subject: Re: [Openstack-operators] Bandwidth limitations
Hi there,
It looks like QOS is already available within the Mitaka release. May
On Wed, Jun 29, 2016 at 12:43 PM, Joseph Bajin 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 a
Thanks for the responses; I'm aware of the QOS policies in Openstack, however I'd like them to be applied automatically. Using predefined flavors as described by Matt Fischer above seems like a good approach, are there any solutions for non-predefined flavors?
- Original message -From: As
To: Joseph Bajin
> Cc: Daniel Levy/Austin/IBM@IBMUS, OpenStack Operators <
> openstack-operators@lists.openstack.org>
> Subject: Re: [Openstack-operators] Bandwidth limitations
> Date: Wed, Jun 29, 2016 12:46 PM
>
> On Wed, Jun 29, 2016 at 12:43 PM, Joseph Bajin
> wrote
Hello,
We are also using it even in Juno. There is one problem with outgoing
traffic limitation made this way if You are using openvswitch also.
This limit is set by libvirt using tc as policing on ingress qdisc.
Openvswitch is using same policing on ingress qdisc if You set
'ingress_policing_rate
