Reviewed: https://review.openstack.org/513398 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1be857435288e4008a41fe67bbc8795dd3d8b134 Submitter: Zuul Branch: master
commit 1be857435288e4008a41fe67bbc8795dd3d8b134 Author: Sławek Kapłoński <[email protected]> Date: Thu Oct 19 14:13:41 2017 +0000 Fix ingress bw limit for OVS DPDK ports For OVS based DPDK ports ingress bandwidth limit is now implemented using egress-policer qos type. Additionally limit values are set in other_config of QoS because there is no queue used in this case. This patch moves also helper methods used to conversion between bytes and bits and between bits and kilobits to neutron.common.utils to be able to use it also in ovs_lib module. Change-Id: I94d1e8dfb82df5c602476db8aaa884ae91fecd7f Closes-Bug: #1724729 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1724729 Title: ovs-lib not support qos type egress-policer for ovs-dpdk Status in neutron: Fix Released Bug description: IN the ovs-dpdk, the Qos cmd use the type "egress-policer", while now the tpye is only "linux-htb" in the ovs-lib.py. May be the type should be setted by config file, on behalf of ovs or ovs-dpdk. The ovs-dpdk qos configure file can be seen: http://docs.openvswitch.org/en/latest/howto/dpdk/ And the normal ovs qos configure file is here: http://docs.openvswitch.org/en/latest/faq/qos/ And the whole cmd line is different. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1724729/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
