QOS Does not work with "policing_rate" and "policing_burst" in qos_driver.py

[Arslan Qadeer]

QOS for OVN does not work with the current options set "policing_rate" and "policing_burst" in qos_driver.py

Steps to reproduce:
1) Create qos-policy
2) Add a bandwidth-limit Rule
3) Create Private network with above qos-policy
4) Spawn VMs in private network

There will be no effect of QOS Policy.

Workaround:

Edit the below file and replace "policing_rate" with "qos_max_rate" and "policing_burst" with "qos_burst"

vi /usr/lib/python2.7/site-packages/networking_ovn/ml2/qos_driver.py

Restart neutron-server

Repeat Steps 1,2,3,4 and now QOS should work.

[Arslan Qadeer (arslanqxgrid)]

Fix Proposed at: https://review.openstack.org/#/c/457518/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/457518
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=f27eaab983a4e4354543f11f32061e38298a2b93
Submitter: Jenkins
Branch: master

commit f27eaab983a4e4354543f11f32061e38298a2b93
Author: Arslan Qadeer <email address hidden>
Date: Tue Apr 18 04:29:16 2017 -0400

     Bug Fix For QOS

     In OvS 2.6，The NorthDB used “policing_burst”，“policing_rate” to config QoS,
     But in OvS2.7 , It changed by “qos_burst”, “qos_max_rate”.

    Change-Id: I8cf1d662c392765d6474abbeff8e6202b6cc970e
    Closes-Bug: #1683073
    Signed-off-by: Arslan Qadeer <email address hidden>

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/networking-ovn 3.0.0.0b2 development milestone.