Adding Memory Overcommitment Manager (MOM) to oVirt

[Carl Trieloff]

On 09/27/2011 09:43 AM, Michael D Day wrote:
> > > 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.


I think the debate has ascertained that we want it. The question is how
we integrate it... (used by VDSM or additional daemon) I like Dor's
suggestion. Let's let the guys figure out the best way to do an initial
integration given where we are at, we play with it, and if in future we
want to evolve the integration we can.

Carl.

Carl.