Bug 1260732 - [BACKWARDS COMPATIBILITY CLEANUP] Remove support for pinning VM to only one CPU
Summary: [BACKWARDS COMPATIBILITY CLEANUP] Remove support for pinning VM to only one CPU
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RestAPI
Version: ---
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.0.0-beta
: 4.0.0
Assignee: Juan Hernández
QA Contact: Artyom
Depends On:
TreeView+ depends on / blocked
Reported: 2015-09-07 14:30 UTC by Juan Hernández
Modified: 2016-07-05 08:03 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-07-05 08:03:19 UTC
oVirt Team: SLA
rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
rule-engine: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
oVirt gerrit 45813 0 master MERGED restapi: Remove the capability to pin a VM to a single host Never

Description Juan Hernández 2015-09-07 14:30:12 UTC
Version 3.6 introduced support for pinning a VM to multiple VMs, preserving the previous capability to pin to only one CPU. In 4.0 we should remove the old mechanism, as the new one is a super-set.

Comment 1 Red Hat Bugzilla Rules Engine 2015-10-19 10:57:13 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 2 Juan Hernández 2016-04-06 12:18:50 UTC
Note that this has been removed from version 4 of the API, but preserved in version 3.

Comment 3 Artyom 2016-06-05 10:55:54 UTC
Verified on rhevm-
Update VM placement policy under v3:
<host id="d4579633-f6a0-4e20-9e56-e5e58b403f4c"/>
<host id="d4579633-f6a0-4e20-9e56-e5e58b403f4c"/>

Comment 4 Sandro Bonazzola 2016-07-05 08:03:19 UTC
oVirt 4.0.0 has been released, closing current release.

Note You need to log in before you can comment on or make changes to this bug.