From: "JR Richardson" <jmr.richardson@gmail.com>
To: <pve-user@lists.proxmox.com>
Subject: [PVE-User] Removing Node from Cluster A and adding to Cluster B
Date: Mon, 15 Nov 2021 21:25:55 -0600 [thread overview]
Message-ID: <000a01d7da99$aa9a2840$ffce78c0$@gmail.com> (raw)
Hey Folks,
Quick question I hope, I have two productions cluster running PVE6 and
working fine, 13 node in one, 4 in another. Bother clusters have separate
switch VLANs and IP space so they are logically isolated. I have a need to
shift a couple of nodes from my larger cluster to my smaller cluster.
My question is after I remove the nodes from one cluster, I'm reading best
practice is to re-install PVE from scratch before adding back to the
cluster. But this is to add it back to the same cluster or is this best
practice regardless of adding to new cluster as well?
Thanks.
JR
next reply other threads:[~2021-11-16 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 3:25 JR Richardson [this message]
2021-11-17 1:09 JR Richardson
2021-11-17 7:22 ` Roland privat
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='000a01d7da99$aa9a2840$ffce78c0$@gmail.com' \
--to=jmr.richardson@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal