From: aderumier@odiso.com
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] proxmox serverfarm - how?
Date: Wed, 03 Mar 2021 09:28:11 +0100 [thread overview]
Message-ID: <05bd2df1ffd2a5762c149abefc7f1afe2b3326b6.camel@odiso.com> (raw)
In-Reply-To: <22970BC8-1653-4B05-AB1C-99E140F8856A@web.de>
Hi, if you have something central, knowning exactly how much nodes are
currently running, and stop/starting them dynamically
you could play with "pvecm expected X" to tell how many vote you need
to have quorum.
(for example, you have 10 nodes builded in corosync, you shutdown 5 of
them --> so no quorum, just use "pvecm expected 5")
Le mercredi 03 mars 2021 à 08:25 +0100, Roland privat a écrit :
> hello,
>
> we want to build an experimental dynamic „datacenter“ in our
> makerspace (mostly for academic purpose), where the number of nodes
> online depends on energy availability, heat demand, processing
> demand, .... , but if i see this right a proxmox cluster needs half
> of the nodes +1 online to have quorum, i.e. for example we wont be
> able to start a vm if only two out of 10 nodes are online.
>
> what‘s the best way to solve this, i.e. what is the most
> secure/consistent way?
>
> eg for a cluster of 10 nodes, what about adding 10 virtual proxmox
> dummy nodes or qdevice instances in another location (so one single
> physical host online has quorum) instead of tuning node/quorum number
> in corosync configuration?
>
> what we want is a „farm“ but not a cluster. but we want centralized
> management and vm migration.
>
> regards
> roland
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2021-03-03 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 7:25 Roland privat
2021-03-03 8:28 ` aderumier [this message]
2021-03-03 11:25 ` Roland
[not found] ` <mailman.67.1614771764.456.pve-user@lists.proxmox.com>
2021-03-03 11:56 ` Roland
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=05bd2df1ffd2a5762c149abefc7f1afe2b3326b6.camel@odiso.com \
--to=aderumier@odiso.com \
--cc=pve-user@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