[one-users] Making scheduler allocation aware
rbabu at hexagrid.com
Fri Oct 29 07:46:38 PDT 2010
We saw that VM's were being deployed to the host where the allocated memory
of all the VM's was higher than the available memory on the host.
We think OpenNebula is executing free command on the host to determine if
there is any room and since free would always return the actual memory that
is being consumed and not the allocated, opennebula would push the new jobs
to the host.
That's the reason we want OpenNebula to be aware of memory allocated to the
VM's on the host.
On Thu, Oct 28, 2010 at 2:02 PM, Javier Fontan <jfontan at gmail.com> wrote:
> Could you describe the problem you had? By default the scheduler will
> not overcommit cpu nor memory.
> On Thu, Oct 28, 2010 at 4:50 AM, Shashank Rachamalla
> <shashank.rachamalla at hexagrid.com> wrote:
> > Hi
> > We have a requirement where in the scheduler should not allow memory over
> > committing while choosing a host for new vm. In order to achieve this, we
> > have changed the way in which FREEMEMORY is being calculated for each
> > FREE MEMORY = TOTAL MEMORY - [ Sum of memory values allocated to VMs
> > are currently running on the host ]
> > Please let us know if the above approach is fine or is there any better
> > to accomplish the task. We are using opennebula 1.4.
> > --
> > Regards,
> > Shashank Rachamalla
> > _______________________________________________
> > Users mailing list
> > Users at lists.opennebula.org
> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> Javier Fontan, Grid & Virtualization Technology Engineer/Researcher
> DSA Research Group: http://dsa-research.org
> Globus GridWay Metascheduler: http://www.GridWay.org
> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
> Users mailing list
> Users at lists.opennebula.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users