From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <d.whyte@proxmox.com>
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 1B7D16022F
for <pve-devel@lists.proxmox.com>; Wed, 7 Oct 2020 10:48:23 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
by firstgate.proxmox.com (Proxmox) with ESMTP id 08D592C6F6
for <pve-devel@lists.proxmox.com>; Wed, 7 Oct 2020 10:48:23 +0200 (CEST)
Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com
[212.186.127.180])
(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 firstgate.proxmox.com (Proxmox) with ESMTPS id 4D86E2C6EE
for <pve-devel@lists.proxmox.com>; Wed, 7 Oct 2020 10:48:22 +0200 (CEST)
Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1])
by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 1114045C0B
for <pve-devel@lists.proxmox.com>; Wed, 7 Oct 2020 10:48:22 +0200 (CEST)
From: Dylan Whyte <d.whyte@proxmox.com>
To: pve-devel@lists.proxmox.com
Date: Wed, 7 Oct 2020 10:48:13 +0200
Message-Id: <20201007084813.1267-1-d.whyte@proxmox.com>
X-Mailer: git-send-email 2.20.1
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-SPAM-LEVEL: Spam detection results: 0
AWL 0.024 Adjusted score from AWL reputation of From: address
KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/,
medium trust
SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record
SPF_PASS -0.001 SPF: sender matches SPF record
Subject: [pve-devel] [PATCH pve-docs] system requirements: minor language
fixup
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>,
<mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
X-List-Received-Date: Wed, 07 Oct 2020 08:48:23 -0000
Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
---
pve-system-requirements.adoc | 28 ++++++++++++++--------------
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/pve-system-requirements.adoc b/pve-system-requirements.adoc
index dc4cc30..bb474ac 100644
--- a/pve-system-requirements.adoc
+++ b/pve-system-requirements.adoc
@@ -4,8 +4,8 @@ ifdef::wiki[]
:pve-toplevel:
endif::wiki[]
-We recommend to use high quality server hardware when running {pve} in
-production. To further decrease the impact of a failed host you can run {pve} in
+We recommend using high quality server hardware, when running {pve} in
+production. To further decrease the impact of a failed host, you can run {pve} in
a cluster with highly available (HA) virtual machines and containers.
{pve} can use local storage (DAS), SAN, NAS, and distributed storage like Ceph
@@ -22,11 +22,11 @@ used in production.
* Intel VT/AMD-V capable CPU/Mainboard for KVM full virtualization support
-* RAM: 1 GB RAM, plus additional RAM used for guests
+* RAM: 1 GB RAM, plus additional RAM needed for guests
* Hard drive
-* One NIC
+* One network card (NIC)
[[install_recommended_requirements]]
@@ -35,8 +35,8 @@ Recommended System Requirements
* Intel EMT64 or AMD64 with Intel VT/AMD-V CPU flag.
-* Memory, minimum 2 GB for the OS and {pve} services. Plus designated memory for
- guests. For Ceph and ZFS additional memory is required; approximately 1GB of
+* Memory: Minimum 2 GB for the OS and {pve} services, plus designated memory for
+ guests. For Ceph and ZFS, additional memory is required; approximately 1GB of
memory for every TB of used storage.
* Fast and redundant storage, best results are achieved with SSDs.
@@ -45,12 +45,12 @@ Recommended System Requirements
or non-RAID with ZFS (optional SSD for ZIL).
* VM storage:
-** For local storage use either a hardware RAID with battery backed write cache
+** For local storage, use either a hardware RAID with battery backed write cache
(BBU) or non-RAID for ZFS and Ceph. Neither ZFS nor Ceph are compatible with a
hardware RAID controller.
** Shared and distributed storage is possible.
-* Redundant (Multi-)Gbit NICs with additional NICs depending on the preferred
+* Redundant (Multi-)Gbit NICs, with additional NICs depending on the preferred
storage technology and cluster setup.
* For PCI(e) passthrough the CPU needs to support the VT-d/AMD-d flag.
@@ -68,13 +68,13 @@ recommended, especially regarding the I/O performance of your system.
Supported Web Browsers for Accessing the Web Interface
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-To access the web-based user interface one of the following browsers is
-recommended:
+To access the web-based user interface, we recommend using one of the following
+browsers:
-* Firefox, a release of the current year, or the latest Extended Support Release
-* Chrome, a release of the current year
+* Firefox, a release from the current year, or the latest Extended Support Release
+* Chrome, a release from the current year
* Microsoft's currently supported version of Edge
-* Safari, a release of the current year
+* Safari, a release from the current year
-When used on a mobile device, {pve} will show a lightweight touch-based
+When accessed from a mobile device, {pve} will show a lightweight, touch-based
interface.
--
2.20.1