[one-users] How to interrogate the scheduler

[Marco Fanti]

I know, but in my configuration I need that the unused hosts are shutted
down, so they are not usable from the scheduler.
What i need is:
before to instantiate or reschedule a VM, i check the scheduler, if the
best host selected from the scheduler is suitable to run the VM, then ok.
If the host is not suitable (e.g. the used_cpu is more than 80% and i don't
want it), then wake up one of the hosts that are in standby and repeat the
procedure.


2014-04-14 15:07 GMT+02:00 Carlo Daffara <carlo.daffara at cloudweavers.eu>:

> There is actually already a scheduler that does it, it uses the "packing
> policy":
> Packing Policy
>
>     Target: Minimize the number of cluster nodes in use
>     Heuristic: Pack the VMs in the cluster nodes to reduce VM fragmentation
>     Implementation: Use those nodes with more VMs running first
>
> RANK = RUNNING_VMS
>
> ( http://archives.opennebula.org/documentation:rel4.4:schg#packing_policy)
> cheers,
> Carlo Daffara
>
> ----- Messaggio originale -----
> Da: "Marco Fanti" <marco.fanti at studenti.polito.it>
> A: "Users OpenNebula" <users at lists.opennebula.org>
> Inviato: Lunedì, 14 aprile 2014 14:54:11
> Oggetto: [one-users] How to interrogate the scheduler
>
> I'm writing a program that has to minimize the number of running hosts.
>
> I need to know, before that I command a VM reschedule or a template
> instantiation, if it is possible to ask to the scheduler which will be the
> selected host.
>
> Kind regards,
> Marco Fanti
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20140414/41435e4e/attachment-0002.htm>