[pve-devel] adding a vm workload scheduler feature

Alexandre DERUMIER aderumier at odiso.com
Tue Nov 17 14:20:56 CET 2015


>>Unless all cluster nodes have identical hardware, how do you determine if a given node is a suitable target for a vm?

I think we could add a manual "host cpu weight" option, because it's difficult to compare cpus performance. (frequencies/nb cores/intel|amd).


>>Also, should there be a flag where you can set the vm to 'allow auto-migration' vs. 'stick to current node'? 

yes !


>>Last but not least, how do you keep the load that migration generates from impacting auto-migration decisions? 

Good question . I think we should use rrds to do average stats of cpu usage.



----- Mail original -----
De: "Martin Waschbüsch" <service at waschbuesch.it>
À: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Mardi 17 Novembre 2015 13:04:16
Objet: Re: [pve-devel] adding a vm workload scheduler feature

> Am 17.11.2015 um 08:23 schrieb Alexandre DERUMIER <aderumier at odiso.com>: 
> 
> Hi, 
> 
> For next year, 
> I would like to implement a new feature : workload scheduler 
> 
> This could allow auto migration of vms, to try to balance the vms across the cluster, 
> from defined rules (for example, try to balance cpu usage) 

Unless all cluster nodes have identical hardware, how do you determine if a given node is a suitable target for a vm? 

Also, should there be a flag where you can set the vm to 'allow auto-migration' vs. 'stick to current node'? 

Last but not least, how do you keep the load that migration generates from impacting auto-migration decisions? 

Martin 
_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 


More information about the pve-devel mailing list