MOM is a policy-driven tool that can be used to manage overcommitment on KVM hosts. Using either libvirt or vdsm, MOM keeps track of active virtual machines on a host. At a regular collection interval, data is gathered about the host and guests. Data can come from multiple sources (eg. the /proc interface, vdsm API calls, libvirt API calls, a client program connected to a guest, etc). Once collected, the data is organized for use by the policy evaluation engine. When started, MOM accepts a user-supplied overcommitment policy. This policy is regularly evaluated using the latest collected data. In response to certain conditions, the policy may trigger reconfiguration of the system’s overcommitment mechanisms. Currently MOM supports control of memory ballooning and KSM but the architecture is designed to accommodate new mechanisms such as cgroups.
Mom – Memory Overcommitment Manager
Important MoM wiki pages
- How Mom is being used to implement :Category:SLA features in oVirt
- Mom project proposal :Project_Proposal_-_MOM and Integration :SLA-mom
- integrated Mom work cycle :Architecture#MOM_integration
- mom policy explained :Sla/host-mom-policy
- Ballooning feature design :Features/Design/memory-balloon and Mom ballooning tech preview :SLA-mom-ballooning-tp
- There is some old documentation that needs to be updated and migrated to this wiki.
- A presentation on overcommitment policy.
- A paper on the same topic.
Additional project information
Our git repository sits on oVirt’s Gerrit server. Development takes place on mostly in vdsm mailing lists: vdsm-patches for submitting new patches, and vdsm-devel for general discussions on where Vdsm development should go. On the latter one, users and potential users should feel comfortable to seek help, ask questions, and get answers about Vdsm.
There is #ovirt on oftc.