[VOTE] Inclusion of memory overcommit manager

[Barak Azulay]

I think this vote is too early,

I would first like to check MOM more, and see the strong/weak points of either 
option.

My gut feeling is that MOM's code should help VDSM to cpmplete its memory 
menagement police (or the entire policy engine). 

There memory policy handling is also required as a part of the VM execution 
(e.g. Monday Morning efect), and as I recall MOM does not handle that.

Bottom line I wouldn't rush too fast,
but if I have to decide now based on what I know and the roadmap ahead I would

-1 

for adding it as a new ovirt project.

but I would certainly start investigate how can the VDSM utilize MOM's code.

Thanks
Barak Azulay



On Tuesday 27 September 2011 20:41:03 Carl Trieloff wrote:
> This vote is to accept into oVirt the memory overcommit manager (mom)
> project either to be used as a dependency in VDSM or as a daemon
> alongside VDSM. This detail will be worked during integration.
> 
> If the project is accepted and given it is our first community submitted
> project to be voted we will create an infrastructure setup list which I
> will record. This can then be used to make it easier for the next
> project joining.
> 
> Please vote -1, 0, +1 whether you would like to include this project
> into oVirt.  I'll leave the vote open at least 72 hours.
> 
> regards
> Carl.
> _______________________________________________
> Board mailing list
> Board at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/board