Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1359484 - [Host QoS] - Engine should take care and apply host QoS on all the networks attached to the same interface and sync them
Summary: [Host QoS] - Engine should take care and apply host QoS on all the networks a...
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.0.0
Hardware: x86_64
OS: Linux
high vote
Target Milestone: ovirt-4.3.0
: ---
QA Contact: Meni Yakove
Depends On:
Blocks: 1302020
TreeView+ depends on / blocked
Reported: 2016-07-24 07:06 UTC by Michael Burman
Modified: 2018-08-01 08:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-08-01 08:03:51 UTC
oVirt Team: Network
rule-engine: ovirt-4.3?
mburman: planning_ack?
mburman: devel_ack?
mburman: testing_ack?

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Bugzilla 1364145 None None None Never

Internal Links: 1364145

Description Michael Burman 2016-07-24 07:06:11 UTC
Description of problem:
[Host QoS] - Engine should take care and apply host QoS on all the networks attached to the same interface and sync them. 

Currently vdsm applying this change below engine's legs and engine consider networks as out-of-sync.  BZ - 1302020

For example: 

1) Attach network 'net1' without host QoS to NIC via setup networks
2) Attach vlan network 'net2' with some host QoS ls=70, rt=200, ul=200 via setup networks to the same NIC

1) caps reports now that 'net1' has ls=70
hostQos': {'out': {'ls': {'d': 0, 'm1': 0, 'm2': 70}}}

2) Engine report that 'net1' is out-of-sync with the host, because there is a difference between the DC and the host.

- Once syncing the network through the engine, the change is gone and engine wins, the 'ls' that was configured over 'net1' is gone. 

* Another scenario that engine should take care is: 
- 2 vlan networks and 1 VM network(non-vlan) attached to one NIC, once we will configure the non-vlan network(default one on qos concept) with some host QoS, it will apply the max value on all of the other vlan networks that are attached to the same interface. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
See description above^^ 

Actual results + Expected results:
Engine should take care such scenarios(and not vdsm) and apply some host QoS('ls' i guess) on all the networks on the interface. He should sync them as well, networks shouldn't be considered as out-of-sync for sync scenarios.

Additional info:
See also

Comment 1 Yaniv Lavi 2018-08-01 08:03:51 UTC
Closing old issues, please reopen if still needed.
In any case patches are welcome.

Note You need to log in before you can comment on or make changes to this bug.