From: Christoph Heiss <c.heiss@proxmox.com>
To: Benjamin Hofer <benjamin@gridscale.io>
Cc: Proxmox VE user list <pve-user@lists.proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>
Subject: Re: [PVE-User] Proxmox VE fully automated installation
Date: Thu, 2 Nov 2023 10:23:07 +0100 [thread overview]
Message-ID: <ki5k6fix53btpaxa6eolv72rpq3bxchi6mgn2wqxzd722qgg73@7mkmu6yxdk6x> (raw)
In-Reply-To: <CAD=jCXM=omA4N3O2ntPFdfykMBnOD4xb0kQMccUKsREUeHe+Pw@mail.gmail.com>
Hi,
On Wed, Nov 01, 2023 at 12:50:23PM +0100, Benjamin Hofer wrote:
>
> Hi all,
>
> is there anyone having resources about fully-automated installation of
> Proxmox VE?
This is currently in the works. Aaron has been working on this for the
last few months and it's coming along nicely this far. It will still
take some time though, as there is a lot to properly flesh out with
something like this, as you can imagine.
Last month an RFC was posted [0], and you are invited to have a look!
Now is the perfect time for feedback, as you might have some ideash of
what you would like to see (or need!) in the auto-installer.
Cc: @Aaron in case you have some more comments on this
> I'd be interested which way is being preferred by the community. I
> think there's no official documentation about that.
If you need it sooner, one possibility is to take a look at automating a
Debian install [1], with Proxmox VE on top of it [2].
[0] https://lists.proxmox.com/pipermail/pve-devel/2023-September/059020.html
[1] https://wiki.debian.org/AutomatedInstallation
[2] https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_12_Bookworm
prev parent reply other threads:[~2023-11-02 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 11:50 Benjamin Hofer
2023-11-02 9:23 ` Christoph Heiss [this message]
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=ki5k6fix53btpaxa6eolv72rpq3bxchi6mgn2wqxzd722qgg73@7mkmu6yxdk6x \
--to=c.heiss@proxmox.com \
--cc=a.lauterer@proxmox.com \
--cc=benjamin@gridscale.io \
--cc=pve-user@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