Bug 1380271

Summary: [OVS] - Add support for Host QoS
Product: [oVirt] vdsm Reporter: Michael Burman <mburman>
Component: CoreAssignee: Edward Haas <edwardh>
Status: CLOSED DEFERRED QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.18.13CC: baptiste.agasse, bugs, danken, info
Target Milestone: ---Flags: danken: ovirt-4.1?
mburman: planning_ack?
mburman: devel_ack?
mburman: testing_ack?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-05 06:24:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1195208    

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?