[one-users] setting hard limits on OpenNebula resources (memory, disk, etc).

[Steven Timm]

It appears that if you include a "CPU=n" in your VM definition
under OpenNebula 3.2, then the corresponding values of
"ACPU" and "AMEN" that show in onehost list/show are decremented
to account for that CPU and memory being used.  If you don't have
that, then the corresponding columns are not decremented.
Furthermore, it appears that there's no way to allocate memory only.

Since the CPU flag is optional, it doesn't seem like this
is a reliable way to make sure everyone obeys the allocated memory
standards.  Have newer opennebula versions gotten better at this?

Steve Timm


On Wed, 4 Dec 2013, Steven Timm wrote:

> I just had a user successfully launch a 64GB VM even though none
> of my hosts have more than 48GB of physical RAM.  All works fine
> until you actually try to use more than 48G of RAM, in which case it goes 
> deep into swap.
>
> Is there any way that OpenNebula can be configured to just outright
> reject VM's that request too many resources?  We are running 3.2 right
> now but would appreciate help for any version.
>
> Steve Timm
>
>
> ------------------------------------------------------------------
> Steven C. Timm, Ph.D  (630) 840-8525
> timm at fnal.gov  http://home.fnal.gov/~timm/
> Fermilab Scientific Computing Division, Scientific Computing Services Quad.
> Grid and Cloud Services Dept., Associate Dept. Head for Cloud Computing
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>

------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525
timm at fnal.gov  http://home.fnal.gov/~timm/
Fermilab Scientific Computing Division, Scientific Computing Services Quad.
Grid and Cloud Services Dept., Associate Dept. Head for Cloud Computing