From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <n.ullreich@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 6142ACC03
 for <pve-devel@lists.proxmox.com>; Mon, 10 Jul 2023 15:50:35 +0200 (CEST)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
 by firstgate.proxmox.com (Proxmox) with ESMTP id 4556318653
 for <pve-devel@lists.proxmox.com>; Mon, 10 Jul 2023 15:50:05 +0200 (CEST)
Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com
 [94.136.29.106])
 (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
 for <pve-devel@lists.proxmox.com>; Mon, 10 Jul 2023 15:50:04 +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 5C4B842949
 for <pve-devel@lists.proxmox.com>; Mon, 10 Jul 2023 15:50:04 +0200 (CEST)
From: Noel Ullreich <n.ullreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Date: Mon, 10 Jul 2023 15:49:50 +0200
Message-Id: <20230710134951.79263-4-n.ullreich@proxmox.com>
X-Mailer: git-send-email 2.39.2
In-Reply-To: <20230710134951.79263-1-n.ullreich@proxmox.com>
References: <20230710134951.79263-1-n.ullreich@proxmox.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.060 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
 T_SCC_BODY_TEXT_LINE    -0.01 -
Subject: [pve-devel] [PATCH pve_docs 1/1] raise min ram requirements to 2
 GiB and specify min disk space
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: Mon, 10 Jul 2023 13:50:35 -0000

Raise the minimum ram required for a PVE instance.
Also specify the minimum and recommended disk space for a PVE instance in GiB.

Signed-off-by: Noel Ullreich <n.ullreich@proxmox.com>
---
 pve-system-requirements.adoc | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/pve-system-requirements.adoc b/pve-system-requirements.adoc
index bb474ac..4e789a4 100644
--- a/pve-system-requirements.adoc
+++ b/pve-system-requirements.adoc
@@ -22,9 +22,9 @@ used in production.
 
 * Intel VT/AMD-V capable CPU/Mainboard for KVM full virtualization support
 
-* RAM: 1 GB RAM, plus additional RAM needed for guests
+* RAM: 2 GiB RAM, plus additional RAM needed for guests
 
-* Hard drive
+* Disk Space: a hard drive with at least a 16 GiB capacity
 
 * One network card (NIC)
 
@@ -35,14 +35,14 @@ 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 for every TB of used storage.
+* Memory: Minimum 4 GiB for the OS and {pve} services, plus designated memory for
+  guests. For Ceph and ZFS, additional memory is required; approximately 1 GiB of
+  memory for every TiB of used storage.
 
 * Fast and redundant storage, best results are achieved with SSDs.
 
 * OS storage: Use a hardware RAID with battery protected write cache (``BBU'')
-  or non-RAID with ZFS (optional SSD for ZIL).
+  or non-RAID with ZFS (optional SSD for ZIL) with at least a 32 GiB capacity.
 
 * VM storage:
 ** For local storage, use either a hardware RAID with battery backed write cache
-- 
2.39.2