Bug 1380271 - [OVS] - Add support for Host QoS
Summary: [OVS] - Add support for Host QoS
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.18.13
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Edward Haas
QA Contact: Michael Burman
URL:
Whiteboard:
: 1667411 (view as bug list)
Depends On:
Blocks: OpenVswitch_Support
TreeView+ depends on / blocked
 
Reported: 2016-09-29 07:21 UTC by Michael Burman
Modified: 2019-01-18 15:14 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-12-05 06:24:36 UTC
oVirt Team: Network
Embargoed:
danken: ovirt-4.1?
mburman: planning_ack?
mburman: devel_ack?
mburman: testing_ack?

Attachments (Terms of Use)

Description Michael Burman 2016-09-29 07:21:36 UTC 
Description of problem:
[OVS] - Add support for Host QoS.

Currently we missing the support to configure a host QoS on a ovs network. 
If trying to set a host QoS on ovs network, we end up with network 'out-of-sync' with the host.

vdsCaps missing the hostQos': {'out': {'ls': {'d': 0, 'm1': 0, 'm2': 50}}},
like we have on legacy networks.

Version-Release number of selected component (if applicable):
vdsm-4.18.13-1.el7ev.x86_64
4.0.4.4-0.1.el7ev
Comment 1 Dan Kenigsberg 2016-12-05 06:24:36 UTC 
Deferring OvS bugs until they are deemed a priority again.
Comment 2 Dominik Holler 2019-01-18 14:46:17 UTC 
*** Bug 1667411 has been marked as a duplicate of this bug. ***
Comment 3 Netbulae 2019-01-18 15:14:49 UTC 
As the QOS is for the whole DC and not configurable for the cluster this is a problem when having a LEGACY cluster and a new (OVS default) cluster in the DC.

Also as OVS is now the default for the latest oVirt releases, are OVS bugs currently not a priority?
Note You need to log in before you can comment on or make changes to this bug.