Adding Memory Overcommitment Manager (MOM) to oVirt

[Michael D Day]

> > So what's the benefit of a separate MOM vs an integrated MOM inside
> > of VDSM?
>
> I'd agree this is really VM policy which should be handled by VDSM.

It's pretty simple. MOM does something valuable today that VDSM doesn't do.
An integrated MOM inside of VDSM doesn't exist. If VDSM wants to
incorporate MOM that's great. But how is the existence of VDSM an argument
against contributing MOM source code to the oVirt community? Am I missing
something?

On a related point, there are good examples that argue for consolidating
function inside a single daemon, and there are good counterexamples. It's
not always true that every node policy function should be integrated within
a single daemon. It probably makes sense in this case. But again, VDSM
doesn't do what MOM does today, which is another argument in favor of
contributing MOM and letting the community work with it.

Thanks,

Mike

Mike Day
IBM Distinguished Engineer
Chief Virtualization Architect, Open Systems Development
Cell: +1 919 371-8786 | mdday at us.ibm.com
http://code.ncultra.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/board/attachments/20110927/b97549b9/attachment.html>