when the free memory is below defined maximum value

 this is the problem, this  statement is veiled in double negatives

When a quantity is below a "Maximum" value then this is should be considered normal
when a quantity exceeds a Maximum value this should be considered an error condition

but this is not the case - when free memory falls below the threshold of MaxFreeMemoryforOverUtlized we are overutilized

On Wed, 13 Jun 2018 at 17:14, Martin Sivak <msivak@redhat.com> wrote:
Hi, it is just a matter of perspective:

MaxFreeMemoryforOverUtlized - the host is considered over utilized
when the free memory is below defined maximum value
MinFreeMemoryforUnderUtilized - the host is considered under utilized
when the free memory is at least the defined minimal value

Best regards

--
Martin Sivak
oVirt


On Wed, Jun 13, 2018 at 7:14 PM, Alastair Neil <ajneil.tech@gmail.com> wrote:
> Can someone clarify these setting for me, I am having difficulty parsing
> what exactly they mean. They seem to me to be backwards.
>
> If I wish to set a threshold at which I want my host to be consider over
> utilized, not schedule any new VMs, and migrate VMs away,  then surely I
> should specify  a minimum threshold of free memory. I.E. if free memory
> drops below my threshold (OR memory use exceed a maximum threshold) migrate
> VM's off of this system.
>
> Conversely if a system is underutilized I should set a maximum threshold of
> free memory (Or minimum used memory).
>
> Thanks,
>
> --Alastair
>
>
> _______________________________________________
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-leave@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/C25Z6WQRPXXU4TMSDDR7HLS5SW3D2LCF/
>