From 9a7396aa6504a78f736e99faaed1c8019522a2de Mon Sep 17 00:00:00 2001 From: Thomas Lamprecht Date: Tue, 13 Nov 2018 13:25:08 +0100 Subject: [PATCH] followup #1850: pvecm: referencing all nodes in etc/hosts is not necessarry ...for a cluster to work, as we can corosync can use multicast to from the totem ring and we then can use that to communicate the other nodes cluster IP. Signed-off-by: Thomas Lamprecht --- pvecm.adoc | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/pvecm.adoc b/pvecm.adoc index 813fe8d..4caca0e 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -92,20 +92,27 @@ Currently the cluster creation can either be done on the console (login via `ssh`) or the API, which we have a GUI implementation for (__Datacenter -> Cluster__). +While it's often common use to reference all other nodenames in `/etc/hosts` +with their IP this is not strictly necessary for a cluster, which normally uses +multicast, to work. It maybe useful as you then can connect from one node to +the other with SSH through the easier to remember node name. + [[pvecm_create_cluster]] Create the Cluster ------------------ Login via `ssh` to the first {pve} node. Use a unique name for your cluster. -This name cannot be changed later. The cluster name follows the same rules as node names. +This name cannot be changed later. The cluster name follows the same rules as +node names. ---- hp1# pvecm create CLUSTERNAME ---- -CAUTION: The cluster name is used to compute the default multicast -address. Please use unique cluster names if you run more than one -cluster inside your network. +CAUTION: The cluster name is used to compute the default multicast address. +Please use unique cluster names if you run more than one cluster inside your +network. To avoid human confusion, it is also recommended to choose different +names even if clusters do not share the cluster network. To check the state of your cluster use: -- 2.39.2