From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 61599D3B5 for ; Wed, 30 Nov 2022 15:09:39 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3E0AA1E6D0 for ; Wed, 30 Nov 2022 15:09:39 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Wed, 30 Nov 2022 15:09:38 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 11BD043C54 for ; Wed, 30 Nov 2022 15:09:38 +0100 (CET) From: Fiona Ebner To: pve-devel@lists.proxmox.com Date: Wed, 30 Nov 2022 15:09:34 +0100 Message-Id: <20221130140934.130359-1-f.ebner@proxmox.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.027 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH docs] cluster join: mention that storage config from cluster is inherited X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Nov 2022 14:09:39 -0000 and what to do about it. It's a rather common topic in forum threads. Suggested in the community forum: https://forum.proxmox.com/threads/118492/post-513743 Signed-off-by: Fiona Ebner --- I just added it to the existing note, but maybe it's better to have two (one about existing guests, one about storage.cfg)? It still felt digestible like this and I wasn't entirely sure what to do about the sentence about the "configuration is overwritten"-sentence if opting to have two notes. pvecm.adoc | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/pvecm.adoc b/pvecm.adoc index 4bf2d53..446735c 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -172,11 +172,14 @@ infrastructure for bigger clusters. Adding Nodes to the Cluster --------------------------- -CAUTION: A node that is about to be added to the cluster cannot hold any guests. -All existing configuration in `/etc/pve` is overwritten when joining a cluster, -since guest IDs could otherwise conflict. As a workaround, you can create a -backup of the guest (`vzdump`) and restore it under a different ID, after the -node has been added to the cluster. +CAUTION: All existing configuration in `/etc/pve` is overwritten when joining a +cluster. In particular, a joining node cannot hold any guests, since guest IDs +could otherwise conflict, and the node will inherit the cluster's storage +configuration. To join a node with existing guest, as a workaround, you can +create a backup of each guest (using `vzdump`) and restore it under a different +ID after joining. If the node's storage layout differs, you will need to re-add +the node's storages, and adapt each storage's node restriction to reflect on +which nodes the storage is actually available. Join Node to Cluster via GUI ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- 2.30.2