Bug 1460160 - The default cluster has "Legacy" migration policy in new deployments
Summary: The default cluster has "Legacy" migration policy in new deployments
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.1.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.1.4
: 4.1.4.1
Assignee: Tomas Jelinek
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-09 09:45 UTC by Michal Skrivanek
Modified: 2017-07-28 14:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-28 14:21:13 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.1?
michal.skrivanek: exception?
michal.skrivanek: planning_ack?
michal.skrivanek: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 79200 0 master MERGED core: change default migration policy of clusters 2017-07-10 08:49:12 UTC
oVirt gerrit 79204 0 ovirt-engine-4.1 MERGED core: change default migration policy of clusters 2017-07-10 10:18:34 UTC

Description Michal Skrivanek 2017-06-09 09:45:40 UTC 
4.x should use a different default migration policy than "Legacy" which is for 3.6 compatibility and provides inferior performance.
It's changeable but we should set the right good default for new installs.
Comment 1 meital avital 2017-07-17 07:58:20 UTC 
Verified on version: 4.1.4.1-0.1.el7
Note You need to log in before you can comment on or make changes to this bug.