Bug #1202

Take into account hypervisor memory consumption on scheduling

Added by Tino Vázquez almost 8 years ago. Updated over 7 years ago.

Status:ClosedStart date:04/02/2012
Priority:NormalDue date:
Assignee:Ruben S. Montero% Done:

0%

Category:-
Target version:Release 3.6
Resolution:fixed Pull request:
Affected Versions:OpenNebula 3.4

Description

Now this is done by taking a 90% of the total memory (grep "threshold" -R *). First step would be to turn it into a configurable value in sched.conf.

Associated revisions

Revision 4bad0444
Added by Carlos Martín over 7 years ago

Bug #1202: Make cpu & mem threshold configurable in sched.conf

Revision 77bb5864
Added by Carlos Martín over 7 years ago

Bug #1202: Make cpu & mem threshold configurable in sched.conf
(cherry picked from commit 4bad0444bf3fa40ab47adc3dd7639100c17536f6)

Revision 1f5d9134
Added by Ruben S. Montero over 7 years ago

feature #1202: Moved hypervisor memory consumption to scheduler, removed from IM probe for vmware

Revision edae49a1
Added by Ruben S. Montero over 7 years ago

feature #1202: Renamed scheduler conf attributes. Change free memory computation

Revision 14983802
Added by Ruben S. Montero over 7 years ago

feature #1202: Moved hypervisor memory consumption to scheduler, removed from IM probe for vmware
(cherry picked from commit 1f5d9134f84ca7636b83a1668dd2a355685cfc47)

Revision d87b6c7b
Added by Ruben S. Montero over 7 years ago

feature #1202: Renamed scheduler conf attributes. Change free memory computation
(cherry picked from commit edae49a15e6e36709ae1047d3dede645ada403ea)

Revision ab543287
Added by Ruben S. Montero over 7 years ago

bug #1202. Remove use of monitoring info to compute available capacity. Now it is based on the allocated
resources for each VM. Reserve a fraction of the host memory fo hypervisor and VM overhead.

Revision 30d57103
Added by Ruben S. Montero over 7 years ago

bug #1202. Remove use of monitoring info to compute available capacity. Now it is based on the allocated
resources for each VM. Reserve a fraction of the host memory fo hypervisor and VM overhead.
(cherry picked from commit ab5432879634319e57973c78b44ccf8c32782f35)

History

#1 Updated by Tino Vázquez almost 8 years ago

A possible refinement could be to adjust the value for cluster or host

#2 Updated by Ruben S. Montero almost 8 years ago

  • Target version set to Release 3.6

#3 Updated by Ruben S. Montero almost 8 years ago

  • Assignee set to Tino Vázquez

#4 Updated by Ruben S. Montero over 7 years ago

  • Target version changed from Release 3.6 to Release 3.8

#5 Updated by Ruben S. Montero over 7 years ago

  • Target version changed from Release 3.8 to Release 3.6

#6 Updated by Ruben S. Montero over 7 years ago

  • Assignee changed from Tino Vázquez to Ruben S. Montero

#7 Updated by Ruben S. Montero over 7 years ago

  • Status changed from New to Assigned

#8 Updated by Ruben S. Montero over 7 years ago

  • Assignee changed from Ruben S. Montero to Carlos Martín

#9 Updated by Ruben S. Montero over 7 years ago

  • Assignee changed from Carlos Martín to Ruben S. Montero

#10 Updated by Ruben S. Montero over 7 years ago

  • Status changed from Assigned to Closed
  • Resolution set to fixed

Also available in: Atom PDF