From: "DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: [pve-devel] cluster resource scheduler question
Date: Tue, 22 Nov 2022 16:43:04 +0000 [thread overview]
Message-ID: <19713dd51749ed24a5ecda1c6930191ed8fc4c11.camel@groupe-cyllene.com> (raw)
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.
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 ?
next reply other threads:[~2022-11-22 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 16:43 DERUMIER, Alexandre [this message]
2022-11-23 9:09 ` Fiona Ebner
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=19713dd51749ed24a5ecda1c6930191ed8fc4c11.camel@groupe-cyllene.com \
--to=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