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 9BB3166AAB for ; Tue, 28 Jul 2020 11:32:23 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8AAB722E3A for ; Tue, 28 Jul 2020 11:32:23 +0200 (CEST) Received: from dev.dominic.proxmox.com (212-186-127-178.static.upcbusiness.at [212.186.127.178]) by firstgate.proxmox.com (Proxmox) with ESMTP id 67CBB22E0C for ; Tue, 28 Jul 2020 11:32:22 +0200 (CEST) Received: by dev.dominic.proxmox.com (Postfix, from userid 0) id 47798201A4; Tue, 28 Jul 2020 11:32:22 +0200 (CEST) From: =?UTF-8?q?Dominic=20J=C3=A4ger?= To: pve-devel@lists.proxmox.com Date: Tue, 28 Jul 2020 11:32:13 +0200 Message-Id: <20200728093215.44860-2-d.jaeger@proxmox.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20200728093215.44860-1-d.jaeger@proxmox.com> References: <20200728093215.44860-1-d.jaeger@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 1 AWL -0.029 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods KHOP_HELO_FCRDNS 0.121 Relay HELO differs from its IP's reverse DNS NO_DNS_FOR_FROM 0.379 Envelope sender has no MX or A DNS records SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Subject: [pve-devel] [PATCH docs 2/4] pvecm: Add comma after 'First' 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: Tue, 28 Jul 2020 09:32:23 -0000 Comma after sequence words like first, next, then, or last. Signed-off-by: Dominic Jäger --- pvecm.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pvecm.adoc b/pvecm.adoc index e7b36c5..390fb4b 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -397,7 +397,7 @@ node from the cluster. WARNING: Ensure all shared resources are cleanly separated! Otherwise you will run into conflicts and problems. -First stop the corosync and the pve-cluster services on the node: +First, stop the corosync and the pve-cluster services on the node: [source,bash] ---- systemctl stop pve-cluster @@ -527,7 +527,7 @@ application. Setting Up A New Network ^^^^^^^^^^^^^^^^^^^^^^^^ -First you have to set up a new network interface. It should be on a physically +First, you have to set up a new network interface. It should be on a physically separate network. Ensure that your network fulfills the xref:pvecm_cluster_network_requirements[cluster network requirements]. @@ -957,7 +957,7 @@ configured to do so. The traffic between the daemon and the cluster must be encrypted to ensure a safe and secure QDevice integration in {pve}. -First install the 'corosync-qnetd' package on your external server and +First, install the 'corosync-qnetd' package on your external server and the 'corosync-qdevice' package on all cluster nodes. After that, ensure that all your nodes on the cluster are online. -- 2.20.1