Open Stack

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' for interface. Problem is that if You spawn new
vm, libvirt configures bandwidth limit with tc but then neutron ovs
agent wants to configure port and is setting vlan_tag in this "tap"
interface. After that operation ovs will clear policing on ingress qdisc
because in ovsdb there is no any info about ingress_policing_rate which
should be set. Details can be found on
http://openvswitch.org/pipermail/discuss/2013-July/010584.html

We solved it by setting libvirt qemu hook
(https://www.libvirt.org/hooks.html) which sets ingress_policing_rate
and ingress_policing_burst in ovs with same values which are in
instance description in libvirt.

About neutron QoS, for now it is possible only to set max bandwidth
limits for traffic outgoing from vm. There is no possiblity to set limit
for incoming traffic.

-- 
Best regards / Pozdrawiam
Sławek Kapłoński
slawek at kaplonski.pl

On Wed, 29 Jun 2016, Matt Fischer wrote:

> 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
>    - vif_inbound_burst
>    - vif_outbound_burst
> 
> 
> 
> On Wed, Jun 29, 2016 at 10:36 AM, 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160703/59dc1408/attachment.pgp>