[pve-devel] [PATCH docs] cluster join: mention that storage config from cluster is inherited

[Fiona Ebner]

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 <f.ebner at proxmox.com>
---

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