[pve-devel] [PATCH docs 5/6] Rewrite: system-requirements

Aaron Lauterer a.lauterer at proxmox.com
Wed Jun 12 16:17:16 CEST 2019


Polished the phrasing in order to make it easer to read and understand.

Signed-off-by: Aaron Lauterer <a.lauterer at proxmox.com>
---
 pve-system-requirements.adoc | 64 ++++++++++++++++++++----------------
 1 file changed, 35 insertions(+), 29 deletions(-)

diff --git a/pve-system-requirements.adoc b/pve-system-requirements.adoc
index e9685cf..f77366d 100644
--- a/pve-system-requirements.adoc
+++ b/pve-system-requirements.adoc
@@ -4,14 +4,15 @@ ifdef::wiki[]
 :pve-toplevel:
 endif::wiki[]
 
-For production servers, high quality server equipment is needed. Keep
-in mind, if you run 10 Virtual Servers on one machine and you then
-experience a hardware failure, 10 services are lost. {pve}
-supports clustering, this means that multiple {pve} installations
-can be centrally managed thanks to the included cluster functionality.
+For production servers it is highly recommended to use quality 
+equipment to reduce the chances of a hardware failure. To further 
+decrease the impact of a failed host {pve} can be
+run in a cluster. A cluster can be set up to support high available
+VMs.
 
 {pve} can use local storage (DAS), SAN, NAS and also distributed
-storage (Ceph RBD). For details see xref:chapter_storage[chapter storage].
+storage like Ceph RBD. For details see xref:chapter_storage[chapter 
+storage].
 
 
 Minimum Requirements, for Evaluation
@@ -19,7 +20,8 @@ Minimum Requirements, for Evaluation
 
 * CPU: 64bit (Intel EMT64 or AMD64)
 
-* Intel VT/AMD-V capable CPU/Mainboard for KVM Full Virtualization support
+* Intel VT/AMD-V capable CPU/Mainboard for KVM Full Virtualization 
+  support
 
 * RAM: 1 GB RAM, plus additional RAM used for guests
 
@@ -33,45 +35,49 @@ Recommended System Requirements
 
 * Intel EMT64 or AMD64 with Intel VT/AMD-V CPU flag.
 
-* Memory, minimum 2 GB for OS and Proxmox VE services. Plus designated memory
-  for guests. For Ceph or ZFS additional memory is required, approximately 1 GB
-  memory for every TB used storage.
+* Memory, minimum 2 GB for OS and Proxmox VE services. Plus designated
+  memory for guests. Additional memory is required for Ceph and ZFS. 
+  Approximately 1 GB of memory for every TB of used storage.
 
-* Fast and redundant storage, best results with SSD disks.
+* Fast and redundant storage, best results are achieved with SSDs.
 
-* OS storage: Hardware RAID with batteries protected write cache (``BBU'') or
-  non-RAID with ZFS and SSD cache.
+* OS storage: Hardware RAID with battery protected write cache
+  (``BBU'') or non-RAID with ZFS and SSD cache.
 
-* VM storage: For local storage use a hardware RAID with battery backed
-  write cache (BBU) or non-RAID for ZFS. Neither ZFS nor Ceph are compatible
-  with a hardware RAID controller. Shared and distributed storage is also
-  possible.
+* VM storage: 
+** For local storage 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 Gbit NICs, additional NICs depending on the preferred storage
-  technology and cluster setup – 10 Gbit and higher is also supported.
+* Redundant Gbit NICs, additional NICs depending on the preferred 
+  storage technology and cluster setup – 10 Gbit and higher is 
+  supported.
 
-* For PCI passthrough a CPU with VT-d/AMD-d CPU flag is needed.
+* For PCI passthrough the CPU needs to support the VT-d/AMD-d flag.
 
 
 Simple Performance Overview
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-On an installed {pve} system, you can run the included `pveperf` script
-to obtain an overview of the CPU and hard disk performance.
+The included `pveperf` tool can be run on an installed {pve} system
+to get an overview of the CPU and hard disk performance.
 
-NOTE: this is just a very quick and general benchmark. More detailed tests
-are recommended, especially regarding the I/O performance of your system.
+NOTE: this is just a very quick and general benchmark. More detailed 
+tests are recommended, especially regarding the I/O performance of 
+your system.
 
 Supported web browsers for accessing the web interface
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-To use the web interface you need a modern browser, this includes:
+A modern web browser is needed to use the web-based management 
+interface. These include:
 
 * Firefox, a release from the current year, or the latest Extended
 Support Release
-* Chrome, a release from the current year
+* Chrome, a release of the current year
 * Microsoft's currently supported versions of Internet Explorer (as
-of 2019, this means IE 11 or IE Edge)
+of 2019, this means IE 11 or Edge)
 * Safari, a release from the current year
 
-If {pve} detects you're connecting from a mobile device, you will be
-redirected to a lightweight touch-based UI.
+When used on a mobile device {pve} will show a lightweight touch-based
+interface.
-- 
2.20.1





More information about the pve-devel mailing list