Change in ovirt-engine[ovirt-engine-3.4]: core: resouces of VMs in launch state shouldn't be committed

[iheim at redhat.com]

Itamar Heim has submitted this change and it was merged.

Change subject: core: resouces of VMs in launch state shouldn't be committed
......................................................................


core: resouces of VMs in launch state shouldn't be committed

Currently we count pending in scheduling process, and committed memory
is calculated in server side according to VMs attached to the host
(including VMs in wait for launch state- host in VM entity
is update when CreateVm command returns from VDSM).
Pending memory is being released in powering-up state, so in fact
we count resources twice: since the time VM is in wait for launch till it's
powering up.

Memory commitment in VDSM occurs after a vm was requested, so using
this data will eliminate VM throttling that failed to reach powering up
state.

Change-Id: Ie2db20c213ac326d620fad578bb5c1c78ff0b3bc
Bug-Url: https://bugzilla.redhat.com/1052024
Signed-off-by: Gilad Chaplik <gchaplik at redhat.com>
---
M backend/manager/modules/vdsbroker/src/main/java/org/ovirt/engine/core/vdsbroker/VdsUpdateRunTimeInfo.java
1 file changed, 7 insertions(+), 3 deletions(-)

Approvals:
  Gilad Chaplik: Verified
  Arik Hadas: Looks good to me, approved



-- 
To view, visit http://gerrit.ovirt.org/25461
To unsubscribe, visit http://gerrit.ovirt.org/settings

Gerrit-MessageType: merged
Gerrit-Change-Id: Ie2db20c213ac326d620fad578bb5c1c78ff0b3bc
Gerrit-PatchSet: 4
Gerrit-Project: ovirt-engine
Gerrit-Branch: ovirt-engine-3.4
Gerrit-Owner: Gilad Chaplik <gchaplik at redhat.com>
Gerrit-Reviewer: Arik Hadas <ahadas at redhat.com>
Gerrit-Reviewer: Gilad Chaplik <gchaplik at redhat.com>
Gerrit-Reviewer: Itamar Heim <iheim at redhat.com>
Gerrit-Reviewer: automation at ovirt.org
Gerrit-Reviewer: oVirt Jenkins CI Server