From 7980581f9fec00cd02844ae07a714b198bfdc9e7 Mon Sep 17 00:00:00 2001 From: Dietmar Maurer Date: Sat, 9 Apr 2016 17:27:27 +0200 Subject: [PATCH] pvecm.adoc: small cleanups --- pvecm.adoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/pvecm.adoc b/pvecm.adoc index 84eb411..1a3a7e8 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -113,10 +113,10 @@ Login via 'ssh' to the node you want to add. For `IP-ADDRESS-CLUSTER` use the IP from an existing cluster node. CAUTION: A new node cannot hold any VM´s, because you would get -conflicts about identical VM IDs. Also, all existing configuration is -overwritten when you join a new node to the cluster. To workaround, -use vzdump to backup and restore to a different VMID after adding -the node to the cluster. +conflicts about identical VM IDs. Also, all existing configuration in +'/etc/pve' is overwritten when you join a new node to the cluster. To +workaround, use vzdump to backup and restore to a different VMID after +adding the node to the cluster. To check the state of cluster: @@ -179,7 +179,7 @@ Move all virtual machines from the node. Make sure you have no local data or backups you want to keep, or save them accordingly. Log in to one remaining node via ssh. Issue a 'pvecm nodes' command to -identify the nodeID: +identify the node ID: ---- hp1# pvecm status -- 2.39.2