Bug 1043230

Summary:	Allow configuring Network QoS on host interfaces
Product:	[oVirt] ovirt-engine	Reporter:	Lior Vernia <lvernia>
Component:	General	Assignee:	Barak <bazulay>
Status:	CLOSED NEXTRELEASE	QA Contact:	Meni Yakove <myakove>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	---	CC:	bazulay, bugs, danken, derez, gklein, lpeer, masayag, mburman, myakove, rbalakri, yeylon, ylavi
Target Milestone:	ovirt-3.6.1	Flags:	danken: ovirt-3.6.z? ylavi: ovirt-4.0.0? ylavi: planning_ack+ rule-engine: devel_ack+ ylavi: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1043226	Environment:
Last Closed:	2015-10-28 11:00:44 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:	1043226, 1271205
Bug Blocks:

Description Lior Vernia 2013-12-15 08:04:45 UTC

+++ This bug was initially created as a clone of Bug #1043226 +++

Currently, it is only possible to shape traffic on VM networks as they make their way into or out of a VM, yet it would be useful to also configure QoS on the physical interfaces of a host. For example, this would allow limiting the bandwidth of a migration network sharing a physical interface with the management network, so that the engine won't lost connectivity to hosts while migration takes place.

Comment 1 Sandro Bonazzola 2014-01-13 13:56:31 UTC

oVirt 3.4.0 alpha has been released including the fix for this issue.

Comment 2 Lior Vernia 2014-01-30 11:47:59 UTC

Moved back to assigned status due to missing implementation on VDSM side, see Bug 1055484 and Bug 1057321.

Comment 6 Michael Burman 2015-10-13 11:37:31 UTC

Blocked by BZ 1271205

Tested on 3.6.0-0.18.el6 with vdsm-4.17.8-1.el7ev.noarch

Comment 7 Red Hat Bugzilla Rules Engine 2015-10-19 10:50:54 UTC

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 8 Red Hat Bugzilla Rules Engine 2015-10-26 16:56:10 UTC

This request has been proposed for two releases. This is invalid flag usage. The higher numbered release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.

Comment 9 Michael Burman 2015-11-26 13:02:26 UTC

Verified on -  3.6.1-0.2.el6 and vdsm-4.17.11-0.el7ev.noarch