Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1113945

Summary:	[RFE] Allow to set migration bandwidth
Product:	[Retired] oVirt	Reporter:	Markus Stockhausen <mst>
Component:	ovirt-engine-config	Assignee:	Doron Fediuck <dfediuck>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.4	CC:	acathrow, gklein, iheim, michal.skrivanek, ofrenkel, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sla
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-06-30 09:28:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Markus Stockhausen 2014-06-27 10:12:38 UTC

Current status:

The maximum migration bandwidth for VM live migrations can be set with /etc/vdsm/vdsm.conf (migration_max_bandwidth = ...). This setting is currently per node. After vdsm installation that value is set to 30MB/sec.  

Idea of RFE:

The migration network is usually well defined (e.g. 1GBit, 10GBit). From that the admin assigns a part of the available bandwidth to migrations. Experience shows that the settings are most of the time the same for all hypervisor nodes. 

Implementation of RFE:

Webgui should provide a setting per cluster that defines the desired migration bandwidth. This will be the default setting for all hosts in the cluster. This setting needs to pe propagated to all vdsms on the corresponding hypervisor nodes. If a single node finds an additional configuration in /etc/vdsm/vdsm.conf that should override the cluster wide setting.

Desired target release:

OVirt 3.6

Comment 1 Omer Frenkel 2014-06-29 08:56:46 UTC

this should be handled as part of bug 1034871
we should consider marking as duplicate..

Comment 2 Markus Stockhausen 2014-06-29 11:55:00 UTC

having no access to BZ994391 I cannot examine if migration bandwidth is fixed or not. Even do not know if it is configurable somewhere.

This bug might be handled as a duplicate of BZ1034871 but to be precise it is only a subset of requested features.

Comment 3 Michal Skrivanek 2014-06-30 09:28:06 UTC

(In reply to Markus Stockhausen from comment #2)
migration bandwidth is not part of any fix yet
since bug 1034871 is preliminarily targeted for 3.6 and bandwidth is the most important to add; I'd close this as a dupe…

currently the only way is in vdsm.conf on each node

*** This bug has been marked as a duplicate of bug 1034871 ***