From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] installation: add section about unattended/automatic installation
Date: Thu, 18 Apr 2024 18:07:42 +0200 [thread overview]
Message-ID: <20240418160742.367029-1-a.lauterer@proxmox.com> (raw)
Mention and briefly explain it. The main part of the documentation will
live in the Wiki for now as it applies to not just Proxmox VE.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
pve-installation.adoc | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/pve-installation.adoc b/pve-installation.adoc
index 274d9ad..e33a8c0 100644
--- a/pve-installation.adoc
+++ b/pve-installation.adoc
@@ -374,6 +374,24 @@ parameter.
Then press `Ctrl-X` or `F10` to boot the configuration.
+[[installation_unattended]]
+Unattended Installation
+-----------------------
+
+It is possible to install {pve} automatically in an unattended manner. This
+makes it possible to fully automate the setup of {pve} on bare-metal. Once the
+installation is done and the host has booted up, automation tools like Ansible
+can be used to further configure the installation.
+
+The options for the installer have to be provided in an answer file. This
+answer file allows using filter rules to decide which disks and network card
+should be used. It is also possible to run custom commands in the installation
+environment prior and after the installation.
+
+It is necessary to prepare the installation ISO to be usable for the automated
+installation. https://pve.proxmox.com/wiki/Automated_Installation[Visit our wiki]
+for more details and information on the unattended installation.
+
ifndef::wiki[]
Install {pve} on Debian
--
2.39.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2024-04-18 16:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240418160742.367029-1-a.lauterer@proxmox.com \
--to=a.lauterer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox