Ovs agent should set min burst value if user don't provide it

Bug #1572670 reported by Slawek Kaplonski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
Slawek Kaplonski

Bug Description

If user will set QoS bw_limit rule without giving burst value (or this burst is set to 0kb) then bw limit could may not work properly with TCP
which is the most common protocol. We should change openvswitch QoS driver to set min burst value as 80 % of configured bw_limit. 80% is value which should works fine for TCP traffic.
Such change will make consistent behaviour between Linuxbridge agent and openvswitch agent. See on https://launchpad.net/bugs/1563720 for LB implementation details.

Changed in neutron:
assignee: nobody → Slawek Kaplonski (slaweq)
Doug Wiegley (dougwig)
Changed in neutron:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/311609

Changed in neutron:
status: Confirmed → In Progress
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/311609
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f766fc71bedc58a0cff0c6dc6e5576f0ab5e2507
Submitter: Jenkins
Branch: master

commit f766fc71bedc58a0cff0c6dc6e5576f0ab5e2507
Author: Sławek Kapłoński <email address hidden>
Date: Sat Apr 30 00:53:22 2016 +0200

    Add setting default max_burst value if not given by user

    If user will not provide burst value for bandwidth limit rule there is
    need to set such value on appropriate to ensure that bandwith limit
    will work fine.
    To ensure at least proper limitation of TCP traffic we decided to set
    burst as 80% of bw_limit value.
    LinuxBridge agent already sets is like that. This patch add same
    behaviour for QoS extension driver in openvswitch L2 agent.

    DocImpact: Add setting default max_burst value in LB and OvS drivers

    Change-Id: Ib12a7cbf88cdffd10c8f6f8442582bf7377ca27d
    Closes-Bug: #1572670

Changed in neutron:
status: In Progress → Fix Released
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/neutron 9.0.0.0b1

This issue was fixed in the openstack/neutron 9.0.0.0b1 development milestone.

tags: added: neutron-proactive-backport-potential
tags: removed: neutron-proactive-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/347017

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/mitaka)

Reviewed: https://review.openstack.org/347017
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8b5d04ff57223885a45dc34e7769a7fd424f7de5
Submitter: Jenkins
Branch: stable/mitaka

commit 8b5d04ff57223885a45dc34e7769a7fd424f7de5
Author: Sławek Kapłoński <email address hidden>
Date: Sat Apr 30 00:53:22 2016 +0200

    Add setting default max_burst value if not given by user

    If user will not provide burst value for bandwidth limit rule there is
    need to set such value on appropriate to ensure that bandwith limit
    will work fine.
    To ensure at least proper limitation of TCP traffic we decided to set
    burst as 80% of bw_limit value.
    LinuxBridge agent already sets is like that. This patch add same
    behaviour for QoS extension driver in openvswitch L2 agent.

    DocImpact: Add setting default max_burst value in LB and OvS drivers

    Conflicts:
     neutron/agent/linux/tc_lib.py

    Change-Id: Ib12a7cbf88cdffd10c8f6f8442582bf7377ca27d
    Closes-Bug: #1572670
    (cherry picked from commit f766fc71bedc58a0cff0c6dc6e5576f0ab5e2507)

tags: added: in-stable-mitaka
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 8.3.0

This issue was fixed in the openstack/neutron 8.3.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.