public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, "DERUMIER,
	Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
Subject: Re: [pve-devel] cluster resource scheduler question
Date: Wed, 23 Nov 2022 10:09:10 +0100	[thread overview]
Message-ID: <aa0a3adc-7a25-4cc3-069b-17f7e1bfb0c7@proxmox.com> (raw)
In-Reply-To: <19713dd51749ed24a5ecda1c6930191ed8fc4c11.camel@groupe-cyllene.com>

Am 22.11.22 um 17:43 schrieb DERUMIER, Alexandre:
> Hi,
> 
> I was looking at the proxmox 7.3 video
> https://www.proxmox.com/en/training/video-tutorials/item/what-s-new-in-proxmox-ve-7-3
> 
> showing the new cluster resource scheduling with static-ressource.
> 
> I'm not sure to understand, but the video seem to say that vm is
> migrated to the least "loaded" node.

yes, the video is misleading there. The static node CPU and memory
values and the configured CPU and memory for guests will be used to
approximate the real usage.

> 
> 
> But looking at static-info of the node,  cpu && memory are the physical
> core number && full memory size
> 
> (in pvestatd,
> 
>     broadcast_static_node_info($maxcpu, $meminfo->{memtotal});
>      my sub broadcast_static_node_info {
>       ...
>         my $info = {
>             cpus => $cpus,
>             memory => $memory,
>      }
> 
> 
> I'm not sure about the logic, but if we only look at number of total
> cpus && memory without current usage, the biggest node will always be
> choose ?  or does I miss something ?

We add the static usage of all active guests (i.e. configured CPU and
memory) to the node's usage. Then, for choosing a node for a guest, we
check how the highest/average CPU/memory usage (in percent) in the
cluster would look like after starting the guest on each node and score
according to those alternatives. In effect, the alternative leading to
the least load (in percent) across the cluster, according to the model
with static guest and node information will be chosen.




  reply	other threads:[~2022-11-23  9:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 16:43 DERUMIER, Alexandre
2022-11-23  9:09 ` Fiona Ebner [this message]
2022-11-23 10:58   ` Thomas Lamprecht
2022-11-23 10:18 ` DERUMIER, Alexandre
2022-11-23 11:28   ` Fiona Ebner
2022-11-23 12:18     ` DERUMIER, Alexandre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aa0a3adc-7a25-4cc3-069b-17f7e1bfb0c7@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=Alexandre.DERUMIER@groupe-cyllene.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal