Request #1242
Handle memory over-committment in OpenNebula
| Status: | Closed | Start date: | 04/18/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | - | |||
| Pull request: |
Description
With the increasing use of KSM, memory over-committment in KVM Hosts is becoming standard procedure.
Currently, Opennebula does not allow summary vm subscription to more memory than the respective host physically provides. OpenNebula should support this great asset, for example using two Memory Statements (MEMORY and VMEMORY) just like it already does vor CPU overcommittment with CPU and VCPU.
This has already been suggested by Carlos MartÃn on the mailing list:
http://lists.opennebula.org/pipermail/users-opennebula.org/2012-February/007884.html
Also, we should prepare for the case that memory is getting physically exhausted. Perhaps employ an existing over-committment managing tool like MOM (https://github.com/aglitke/mom/wiki/).
Related issues
Updated by