Bug 1266041 - Confusing VM pinning to Host behaviour
Summary: Confusing VM pinning to Host behaviour
Keywords:
Status: CLOSED DUPLICATE of bug 1254818
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.0.0-alpha
: ---
Assignee: Roy Golan
QA Contact: Artyom
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-24 11:36 UTC by Roy Golan
Modified: 2016-03-20 10:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-20 10:06:27 UTC
oVirt Team: SLA
Embargoed:
dfediuck: ovirt-4.0.0?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1243811 0 high CLOSED vm with dedicate host fails to run on other host, if dedicated host is in maintenance 2021-02-22 00:41:40 UTC

Internal Links: 1243811

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 ***
Note You need to log in before you can comment on or make changes to this bug.