From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] installation: unattended: sync the section with the wiki introduction
Date: Mon, 10 Feb 2025 15:06:15 +0100 [thread overview]
Message-ID: <20250210140615.3-1-a.zeidler@proxmox.com> (raw)
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
next reply other threads:[~2025-02-10 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 14:06 Alexander Zeidler [this message]
2025-02-19 17:06 ` [pve-devel] applied: " Aaron Lauterer
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=20250210140615.3-1-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.