From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>,
"DERUMIER, Alexandre" <Alexandre.DERUMIER@groupe-cyllene.com>
Subject: Re: [pve-devel] cluster resource scheduler question
Date: Wed, 23 Nov 2022 11:58:22 +0100 [thread overview]
Message-ID: <03397d75-f6a4-2d7b-e943-bb5a1de60ac3@proxmox.com> (raw)
In-Reply-To: <aa0a3adc-7a25-4cc3-069b-17f7e1bfb0c7@proxmox.com>
Am 23/11/2022 um 10:09 schrieb Fiona Ebner:
>> 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.
>
Not really misleading. It's the least loaded node, there's just more ways to
determine load and the current mode is for static-load (vs. dynamic runtime
load, planned for a next release).
Am 22/11/2022 um 17:43 schrieb DERUMIER, Alexandre:
> 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 ?
Well yes, until it's "filled" enough for other nodes to be more favorable,
a "bigger" node can host more after all.
Am 23/11/2022 um 11:18 schrieb DERUMIER, Alexandre:
> (BTW, I don't see the repo in proxmox git ?)
fixed now, thanks for the reminder
next prev parent reply other threads:[~2022-11-23 10:58 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
2022-11-23 10:58 ` Thomas Lamprecht [this message]
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=03397d75-f6a4-2d7b-e943-bb5a1de60ac3@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=Alexandre.DERUMIER@groupe-cyllene.com \
--cc=f.ebner@proxmox.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