Bug 1036638

Summary: [RFE] VM-VM Affinity
Product: [Retired] oVirt Reporter: Gilad Chaplik <gchaplik>
Component: ovirt-engine-coreAssignee: Gilad Chaplik <gchaplik>
Status: CLOSED CURRENTRELEASE QA Contact: Artyom <alukiano>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.4CC: acathrow, dfediuck, howey.vernon, iheim, juan.hernandez, knesenko, mavital, pbandark, yeylon
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sla
Fixed In Version: ovirt-3.4.0-beta1 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-31 15:04: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:

Description Gilad Chaplik 2013-12-02 11:48:25 UTC 
The oVirt scheduler capabilities introduced in version 3.3 have opened opportunities to enhance how VM Workloads are scheduled to run within a cluster.  By using the filtering and weighing mechanisms introduced in the Scheduler, it is now possible to apply Affinity and Anti-Affinity rules to VMs to manually dictate scenarios in which VMs should run together on the same, or separately on different hosts.

Define a positive/negative (anti) mandatory/optional (must/should) affinity object that can be attached to VMs, and according to this object the scheduler will place the VM.
Comment 1 Artyom 2014-02-24 09:30:16 UTC 
Verified on ovirt-engine-3.4.0-0.11.beta3.el6.noarch
Verified after manual running of test plan  https://tcms.engineering.redhat.com/plan/12145/
Comment 2 Juan Hernández 2014-03-03 13:10:33 UTC 
Note that the RESTAPI support for affinity groups won't be included in 3.4.0, it will be in 3.4.1 instead.
Comment 3 Sandro Bonazzola 2014-03-31 15:04:06 UTC 
This is an automated message: moving to Closed CURRENT_RELEASE since oVirt 3.4.0 has been released.