all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 1/7] system-requirements: revise subchapter and provide more details
Date: Tue,  4 Mar 2025 16:40:55 +0100	[thread overview]
Message-ID: <20250304154101.3-2-a.zeidler@proxmox.com> (raw)
In-Reply-To: <20250304154101.3-1-a.zeidler@proxmox.com>

Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
---
 pve-system-requirements.adoc | 29 ++++++++++++++++++++---------
 1 file changed, 20 insertions(+), 9 deletions(-)

diff --git a/pve-system-requirements.adoc b/pve-system-requirements.adoc
index 8a982a8..82d9be5 100644
--- a/pve-system-requirements.adoc
+++ b/pve-system-requirements.adoc
@@ -1,3 +1,4 @@
+[[system_requirements]]
 System Requirements
 -------------------
 ifdef::wiki[]
@@ -6,7 +7,8 @@ endif::wiki[]
 
 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.
+a cluster with xref:chapter_ha_manager[highly available (HA)] virtual
+machines and containers.
 
 {pve} can use local storage (DAS), SAN, NAS, and distributed storage like Ceph
 RBD. For details see xref:chapter_storage[chapter storage].
@@ -26,7 +28,9 @@ used in production.
 
 * Hard drive
 
-* One network card (NIC)
+* One network card (NIC), used for fetching system updates and access
+via xref:chapter_gui[web interface], `ssh` or
+link:api-viewer/index.html[{pve} API]
 
 
 [[install_recommended_requirements]]
@@ -39,15 +43,22 @@ Recommended System Requirements
   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.
+* Fast and redundant storage, best results are achieved with SSDs. Do
+  not use SD cards or USB flash drives, as these have a lower
+  durability and performance.
 
-* OS storage: Use a hardware RAID with battery protected write cache (``BBU'')
-  or non-RAID with ZFS (optional SSD for ZIL).
+* OS storage:
+** An HBA with a redundant xref:chapter_zfs[ZFS] RAID level. If not
+   using fast enterprise SSDs with power-loss protection, optionally
+   add one for use as xref:sysadmin_zfs_add_cache_and_log_dev[SLOG].
+** Or a hardware RAID controller with battery-backed write cache (BBU)
+   and not ZFS, as the combination can lead to data loss.
 
 * 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.
+** For local storage, the same recommendations apply as for OS
+   storage. However, if a hardware RAID controller is used, in
+   addition to ZFS, xref:chapter_pveceph[Ceph] is also incompatible
+   with it.
 ** Shared and distributed storage is possible.
 ** SSDs with Power-Loss-Protection (PLP) are recommended for good performance.
   Using consumer SSDs is discouraged.
@@ -75,7 +86,7 @@ browsers:
 
 * 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
+* Edge, Microsoft's currently supported release
 * Safari, a release from the current year
 
 When accessed from a mobile device, {pve} will show a lightweight, touch-based
-- 
2.39.5



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2025-03-04 15:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 15:40 [pve-devel] [PATCH v1 docs 0/7] Revise installation chapter Alexander Zeidler
2025-03-04 15:40 ` Alexander Zeidler [this message]
2025-03-04 16:21   ` [pve-devel] [PATCH docs 1/7] system-requirements: revise subchapter and provide more details Shannon Sterz
2025-03-04 15:40 ` [pve-devel] [PATCH docs 2/7] installation: prepare medium: revise subchapter Alexander Zeidler
2025-03-04 16:34   ` Shannon Sterz
2025-03-04 15:40 ` [pve-devel] [PATCH docs 3/7] installation: revise introduction Alexander Zeidler
2025-03-05  8:35   ` Shannon Sterz
2025-03-04 15:40 ` [pve-devel] [PATCH docs 4/7] installer: " Alexander Zeidler
2025-03-05  8:53   ` Shannon Sterz
2025-03-04 15:40 ` [pve-devel] [PATCH docs 5/7] installer: revise boot menu description and introduce sections Alexander Zeidler
2025-03-04 15:41 ` [pve-devel] [PATCH docs 6/7] installer: revise installation steps " Alexander Zeidler
2025-03-05  9:25   ` Shannon Sterz
2025-03-04 15:41 ` [pve-devel] [PATCH docs 7/7] installer: revise intro of advanced ZFS/BTRFS configuration options Alexander Zeidler
2025-03-05  9:27   ` Shannon Sterz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250304154101.3-2-a.zeidler@proxmox.com \
    --to=a.zeidler@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal