all lists on lists.proxmox.com
 help / color / mirror / Atom feed
* [pve-devel] [PATCH docs] cluster join: mention that storage config from cluster is inherited
@ 2022-11-30 14:09 Fiona Ebner
  2023-01-16 15:55 ` [pve-devel] applied: " Thomas Lamprecht
  0 siblings, 1 reply; 2+ messages in thread
From: Fiona Ebner @ 2022-11-30 14:09 UTC (permalink / raw)
  To: pve-devel

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@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





^ permalink raw reply	[flat|nested] 2+ messages in thread

* [pve-devel] applied: [PATCH docs] cluster join: mention that storage config from cluster is inherited
  2022-11-30 14:09 [pve-devel] [PATCH docs] cluster join: mention that storage config from cluster is inherited Fiona Ebner
@ 2023-01-16 15:55 ` Thomas Lamprecht
  0 siblings, 0 replies; 2+ messages in thread
From: Thomas Lamprecht @ 2023-01-16 15:55 UTC (permalink / raw)
  To: Proxmox VE development discussion, Fiona Ebner

Am 30/11/2022 um 15:09 schrieb 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@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(-)
> 
>

applied, thanks!




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-01-16 15:55 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-30 14:09 [pve-devel] [PATCH docs] cluster join: mention that storage config from cluster is inherited Fiona Ebner
2023-01-16 15:55 ` [pve-devel] applied: " Thomas Lamprecht

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