From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id 08FCE1FF173
	for <inbox@lore.proxmox.com>; Mon, 10 Feb 2025 15:07:02 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 755F4EB23;
	Mon, 10 Feb 2025 15:06:58 +0100 (CET)
From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pve-devel@lists.proxmox.com
Date: Mon, 10 Feb 2025 15:06:15 +0100
Message-Id: <20250210140615.3-1-a.zeidler@proxmox.com>
X-Mailer: git-send-email 2.39.5
MIME-Version: 1.0
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.090 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
 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
 Validity was blocked. See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
 RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
 Validity was blocked. See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
 RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to
 Validity was blocked. See
 https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more
 information.
 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 docs] installation: unattended: sync the section
 with the wiki introduction
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>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>

so that there are not two different versions of the introduction and
users mistakenly think they have already read the introduction in the
admin guide.

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

diff --git a/pve-installation.adoc b/pve-installation.adoc
index 869a879..588eeee 100644
--- a/pve-installation.adoc
+++ b/pve-installation.adoc
@@ -406,17 +406,24 @@ Then press `Ctrl-X` or `F10` to boot the configuration.
 Unattended Installation
 -----------------------
 
-It is possible to install {pve} automatically in an unattended manner. This
-enables you to fully automate the setup process on bare-metal. Once the
-installation is complete and the host has booted up, automation tools like
-Ansible can be used to further configure the installation.
+The automated installation method allows installing a Proxmox solution
+in an unattended manner. This enables you to fully automate the setup
+process on bare-metal. Once the installation is complete and the host
+has booted up, automation tools like Ansible can be used to further
+configure the installation.
 
-The necessary options for the installer must be provided in an answer file. This
-file allows the use of filter rules to determine which disks and network cards
-should be used.
+The necessary options for the installer must be provided in an answer
+file. This file allows using filter rules to determine which disks and
+network cards should be used.
+
+To use the automated installation, it is first necessary to choose a
+source from which the answer file is fetched from and then prepare an
+installation ISO with that choice.
+
+Once the ISO is prepared, its initial boot menu will show a new boot
+entry named "Automated Installation" which gets automatically selected
+after a 10-second timeout.
 
-To use the automated installation, it is first necessary to prepare an
-installation ISO.
 https://pve.proxmox.com/wiki/Automated_Installation[Visit our wiki] for more
 details and information on the unattended installation.
 
-- 
2.39.5



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