On 2/5/20 3:17 PM, Aaron Lauterer wrote:
improve phrasing, align headlines, rearrange requirement lists
Signed-off-by: Aaron Lauterer <a.laute...@proxmox.com>
---
v2 -> v3:
rebased on current master
v1 -> v2:
applied (some) suggestions from oguz [0], IO performance is based on the
whole system, not just disks
[0] https://pve.proxmox.com/pipermail/pve-devel/2019-September/038953.html
pve-system-requirements.adoc | 65 +++++++++++++++++++-----------------
1 file changed, 34 insertions(+), 31 deletions(-)
diff --git a/pve-system-requirements.adoc b/pve-system-requirements.adoc
index 0a4ba6c..63f8a37 100644
--- a/pve-system-requirements.adoc
+++ b/pve-system-requirements.adoc
@@ -4,22 +4,23 @@ 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.
+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
+a cluster with highly available (HA) virtual machines and containers.
-{pve} can use local storage (DAS), SAN, NAS and also distributed
-storage (Ceph RBD). For details see xref:chapter_storage[chapter storage].
+{pve} can use local storage (DAS), SAN, NAS, and distributed storage like Ceph
+RBD. For details see xref:chapter_storage[chapter storage].
[[install_minimal_requirements]]
Minimum Requirements, for Evaluation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+These minimum requirements are for evaluation purposes only and should not be
+used in production.
+
* 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
@@ -34,44 +35,46 @@ 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 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 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: Use a hardware RAID with battery protected write cache (``BBU'')
+ or non-RAID with ZFS and SSD cache.
This is probably a given, but an SSD cache only makes sense when not
already using SSDs, might make sense to note that here - though I can't
come up with a concise way of putting it.
-* 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 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 Gbit NICs, additional NICs depending on the preferred storage
- technology and cluster setup – 10 Gbit and higher is also supported.
+ technology and cluster setup (10 Gbit and higher) are supported.
This changes the meaning from "10 Gbit is supported" to "additional
links are supported". Both are true, how about:
* Redundant (Multi-)Gbit NICs, additional NICs depending on the
preferred storage technology and cluster setup
-* For PCI passthrough a CPU with VT-d/AMD-d CPU flag is needed.
+* For PCI(e) passthrough the CPU needs to support the VT-d/AMD-d flag.
-Simple Performance Overview
+Simple performance overview
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Why change the capitalization? Although our heading capitalization in
general is a bit all over the place, we seem to be mostly using Title
Case [0] elsewhere (e.g. the system requirements above) - which I
personally prefer, though it's a matter of opinion.
[0] https://en.wikipedia.org/wiki/Letter_case#Title_case
-On an installed {pve} system, you can run the included `pveperf` script
-to obtain an overview of the CPU and hard disk performance.
+To get an overview of the CPU and hard disk performance on an installed {pve}
+system, run the included `pveperf` tool.
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:
-* Firefox, a release from the current year, or the latest Extended
-Support Release
-* Chrome, a release from the current year
-* Microsofts currently supported version of Edge
-* Safari, a release from the current year
+To access the web-based user interface one of the following browsers is
+recommended:
+
+* Firefox, a release of the current year, or the latest Extended Support
Release
+* Chrome, a release of the current year
+* Microsoft's currently supported version of Edge
+* Safari, a release of 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.
_______________________________________________
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
