Re: [pve-devel] adding a vm workload scheduler feature

ould use rrds to do average stats of cpu usage. - Mail original - De: "Martin Waschbüsch" <serv...@waschbuesch.it> À: "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mardi 17 Novembre 2015 13:04:16 Objet: Re: [pve-devel] adding a vm workload scheduler feature >

Re: [pve-devel] adding a vm workload scheduler feature

> Am 17.11.2015 um 08:23 schrieb Alexandre DERUMIER : > > 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,

Re: [pve-devel] adding a vm workload scheduler feature

> On November 17, 2015 at 4:37 PM Dietmar Maurer wrote: > > > > >>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. >

Re: [pve-devel] adding a vm workload scheduler feature

> On November 17, 2015 at 4:43 PM Michael Rasmussen wrote: > > > On Tue, 17 Nov 2015 11:01:58 +0100 (CET) > Alexandre DERUMIER wrote: > > > > > I'm thinked to use rrd files to have stats on a long time. (maybe do average > > on last x minutes) > > >

Re: [pve-devel] adding a vm workload scheduler feature

On Tue, 17 Nov 2015 11:01:58 +0100 (CET) Alexandre DERUMIER wrote: > > I'm thinked to use rrd files to have stats on a long time. (maybe do average > on last x minutes) > > (for example we don't want to migrate a vm if the host is overload for 1 or 2 > minutes, > because

Re: [pve-devel] adding a vm workload scheduler feature

On Tue, 17 Nov 2015 11:01:58 +0100 (CET) Alexandre DERUMIER wrote: > yes, sure. I just want to start with cpu, but memory could be add too. > > I'm not sure for io-wait, as migrating the vm don't change the storage ? > Is that also the case for Gluster? --

Re: [pve-devel] adding a vm workload scheduler feature

> >>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. I think that any load/cpu metric will be difficult(unstable). I would simply use static values

Re: [pve-devel] adding a vm workload scheduler feature

Am 17.11.2015 um 14:56 schrieb Martin Waschbüsch: Am 17.11.2015 um 14:20 schrieb Alexandre DERUMIER : 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"

Re: [pve-devel] adding a vm workload scheduler feature

quot; <pve-devel@pve.proxmox.com> Envoyé: Mardi 17 Novembre 2015 15:26:15 Objet: Re: [pve-devel] adding a vm workload scheduler feature Am 17.11.2015 um 14:56 schrieb Martin Waschbüsch: >> Am 17.11.2015 um 14:20 schrieb Alexandre DERUMIER <aderum...@odiso.com>: >> >>&

Re: [pve-devel] adding a vm workload scheduler feature

evel@pve.proxmox.com> Envoyé: Mardi 17 Novembre 2015 14:56:39 Objet: Re: [pve-devel] adding a vm workload scheduler feature > Am 17.11.2015 um 14:20 schrieb Alexandre DERUMIER <aderum...@odiso.com>: > >>> Unless all cluster nodes have identical hardware, how do you determ

Re: [pve-devel] adding a vm workload scheduler feature

rum...@odiso.com>, "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mardi 17 Novembre 2015 16:51:23 Objet: Re: [pve-devel] adding a vm workload scheduler feature > On November 17, 2015 at 4:37 PM Dietmar Maurer <diet...@proxmox.com> wrote: > > > > >>

Re: [pve-devel] adding a vm workload scheduler feature

> But indeed, dynamic stats is not easy to resolve. > > > Ovirt has a planned feature which use optaplanner > > http://www.ovirt.org/Features/Optaplanner > This seem to do some kind of heuristics and maths (out of my competence ;), to > known which vm migrate. IMHO you can always generate a

Re: [pve-devel] adding a vm workload scheduler feature

ot;pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mardi 17 Novembre 2015 08:40:19 Objet: Re: [pve-devel] adding a vm workload scheduler feature > What do you think about it ? interesting > > As we don't have master node, I don't known how to implement this: > > 1) each

Re: [pve-devel] adding a vm workload scheduler feature

Il 17 novembre 2015 08:40:19 CET, Dietmar Maurer ha scritto: > >> What do you think about it ? > >interesting > >> >> As we don't have master node, I don't known how to implement this: >> >> 1) each node try to migrate his own vms to another node with less cpu >usage.

Re: [pve-devel] adding a vm workload scheduler feature

Hi all, On 2015-11-17 08:23, Alexandre DERUMIER wrote: What do you think about it ? Sounds great, but I think memory and io-wait should be part of the list as well. As we don't have master node, I don't known how to implement this: 1) each node try to migrate his own vms to another

Re: [pve-devel] adding a vm workload scheduler feature

nom.net" <m...@datanom.net> À: "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mardi 17 Novembre 2015 10:11:40 Objet: Re: [pve-devel] adding a vm workload scheduler feature Hi all, On 2015-11-17 08:23, Alexandre DERUMIER wrote: > > > What do you think about it ? > So

[pve-devel] adding a vm workload scheduler feature

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) ovirt and vmware have this kind of feature :

Re: [pve-devel] adding a vm workload scheduler feature

> What do you think about it ? interesting > > As we don't have master node, I don't known how to implement this: > > 1) each node try to migrate his own vms to another node with less cpu usage. >maybe with a global cluster lock to not have 2 nodes migrating in both way > at the same