Bug 1266041

Summary:	Confusing VM pinning to Host behaviour
Product:	[oVirt] ovirt-engine	Reporter:	Roy Golan <rgolan>
Component:	Backend.Core	Assignee:	Roy Golan <rgolan>
Status:	CLOSED DUPLICATE	QA Contact:	Artyom <alukiano>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.0.0	CC:	bugs, dfediuck, mavital, mgoldboi
Target Milestone:	ovirt-4.0.0-alpha	Flags:	dfediuck: ovirt-4.0.0? rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-20 10:06:27 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Roy Golan 2015-09-24 11:36:51 UTC

Description of problem:

The behaviour and the concept of Vm pinning is causing confusion both in usage and development and affects related parts of the application like: HA, CPU pining, Pin-to-host, PCI-passthrough etc.

We need to define the behaviour and interactions of
Pin-To-Host, Migration Options, Run, Run-Once, and Migrate and their part in the implementation. 

On top of that, The UI doesn't reflect the mix of behaviour e.g it is not clear what is going to happen when choosing assigning a Host to a Vm to run on, with combinations of Migration Options, and have the Hosts being unavailable.

Comment 1 Doron Fediuck 2016-03-20 10:06:27 UTC


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