Bug 1043233

Summary: Balancing cluster doesn't add VM's Predicted CPU load into acceptable hosts load
Product: Red Hat Enterprise Virtualization Manager Reporter: Gilad Chaplik <gchaplik>
Component: ovirt-engineAssignee: Gilad Chaplik <gchaplik>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Svaty <lsvaty>
Severity: high Docs Contact:
Priority: high    
Version: 3.3.0CC: acathrow, dfediuck, eedri, gchaplik, iheim, lpeer, lsvaty, mavital, Rhev-m-bugs, sherold, yeylon
Target Milestone: ---   
Target Release: 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sla
Fixed In Version: org.ovirt.engine-root-3.4.0-16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:

Description Gilad Chaplik 2013-12-15 08:34:36 UTC 
Description of problem:
When balancing a cluster, the balancing logic should return a VM and acceptable hosts, while filtering those hosts the scheduler doesn't take into account the predicted VM CPU load.

How reproducible:
100%

Steps to Reproduce:
0. have a 2 similar hosts cluster and enable load balancing in cluster policy.
1. create a VM that consume all host CPU resources.


Actual results:
The vm bounces between 2 hosts

Expected results:
The scheduler should identify, that migrating the VM will cause the host to exceed its CPU load, and shouldn't balance that VM.

Additional info:
predictedVmCpu = (vm.usageCpuPercent * vm.numOfCpus) / host.effectiveCpuCores
Comment 1 Eyal Edri 2014-02-10 09:45:56 UTC 
moving to 3.3.2 since 3.3.1 was built and moved to QE.
Comment 3 Lukas Svaty 2014-04-30 14:14:04 UTC 
verified in av8, no more bouncing VMs

event:
2014-Apr-30, 16:09
Used CPU of host 10.34.62.204 [96%] exceeded defined threshold [95%].

log:
2014-04-30 16:12:02,449 INFO  [org.ovirt.engine.core.bll.scheduling.PolicyUnitImpl] (DefaultQuartzScheduler_Worker-41) VdsLoadBalancer: vm selection - selected vm: stressed-vm, cpu: 12. => no migration
Comment 4 Itamar Heim 2014-06-12 14:11:30 UTC 
Closing as part of 3.4.0