public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
From: aderumier@odiso.com
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
	 "pve-user@pve.proxmox.com" <pve-user@pve.proxmox.com>
Subject: Re: [PVE-User] BIG cluster questions
Date: Sat, 26 Jun 2021 13:16:27 +0200	[thread overview]
Message-ID: <e8199a1f66fa65f2cf493c88d0ef2c25980e2a64.camel@odiso.com> (raw)
In-Reply-To: <mailman.16.1624545042.464.pve-user@lists.proxmox.com>

Le jeudi 24 juin 2021 à 16:30 +0200, Eneko Lacunza via pve-user a
écrit :
> Now for more general questions; do you think a 88-node Proxmox VE 
> cluster is feasible?

Well, corosync is not really done to this amount of node. (I think the
hardcoded limit is around 100),
but in practice, I have seen a lot of users having problem with
corosync communication starting around 30 nodes

(Maybe with low-latency switches + fast frequencies cpu, it's possible
to keep latency enough low to get it working)


> Those 88 nodes will host about 14.000 VMs. Will HA manager be able to
> manage them, or are they too many? (HA for those VMs doesn't seem to
> be 
> a requirement right know).

I have cluster with 2500vms, it's working fine. (on a 15 nodes cluster
with around 200vms on each node).
I don't known with 15000vms, maybe the main pve-crm loop will take more
time, I'm not sure about the timeouts.


At work, I'm doing nodes 20 nodes cluster (1 by rack) to avoid to have
big cluster.
Multi-cluster central management is not yet on the roadmap, but they
are some tool like
https://maas.io/
which allow to manage multi-cluster in a central way. 



  parent reply	other threads:[~2021-06-26 11:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.16.1624545042.464.pve-user@lists.proxmox.com>
2021-06-25 17:33 ` Laurent Dumont
2021-06-26 11:16 ` aderumier [this message]
2021-06-26 12:59 JR Richardson
     [not found] <a4c39bce-b416-1286-3374-fc73afa41125@binovo.es>
2021-06-28  9:32 ` Thomas Lamprecht

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=e8199a1f66fa65f2cf493c88d0ef2c25980e2a64.camel@odiso.com \
    --to=aderumier@odiso.com \
    --cc=pve-user@lists.proxmox.com \
    --cc=pve-user@pve.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