From: Christoph Heiss <c.heiss@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Aaron Lauterer <a.lauterer@proxmox.com>
Subject: Re: [pve-devel] [RFC installer 2/6] add proxmox-auto-installer
Date: Thu, 21 Sep 2023 13:39:31 +0200 [thread overview]
Message-ID: <7pceqwz6s5zqrkkkaqww4plzhwgzgjsgxwfdjqj7hxwostkds3@hbaxjh7zdrjs> (raw)
In-Reply-To: <539fc219-86cc-43e7-b2c6-470c068169fb@proxmox.com>
On Thu, Sep 21, 2023 at 01:30:33PM +0200, Thomas Lamprecht wrote:
>
> Am 21/09/2023 um 13:16 schrieb Christoph Heiss:
[..]
> > Sending simple JSON-formatted logs to an HTTP endpoint or even using
> > the rsyslog protocol come to mind and would be a good solution for
> > this, I think.
> > Or, if the answer file is read from an (USB drive) partition, write
> > the log there?
>
> I think this should be added to the config as option and default to
> "stop-and-wait-for-human-intervention", i.e., show error in a prompt
> and wait.
Yeah, seems even better to make it a conscious choice for
administrators with a sensible default.
>
> We can then add other reporting mechanisms in the future, possibly
> dependent on where the config is pulled from.
>
[..]
> > Further, a way to run commands in the finished installation chroot could
> > be pretty useful too, e.g. to create some files in /etc comes to mind.
>
> I would like to avoid having such things from the start, let's keep
> it simple for now and collect feedback when this is then released.
> As then, we can decide which mechanism make sense as native feature
> and if we really want such a general hook that can allow users to
> break lots off stuff and assumptions and still say "well I used the
> official installer", i.e., cause support overhead.
No objections here either - I was just spilling out some of my thoughts
while messing around with it for testing.
Esp. the latter is quite a good point, how to handle that "correctly"
without causing us pain.
next prev parent reply other threads:[~2023-09-21 11:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 13:28 [pve-devel] [RFC installer 0/6] add automated installation Aaron Lauterer
2023-09-05 13:28 ` [pve-devel] [RFC installer 1/6] low level: sys: fetch udev properties Aaron Lauterer
2023-09-05 13:28 ` [pve-devel] [RFC installer 2/6] add proxmox-auto-installer Aaron Lauterer
2023-09-21 11:16 ` Christoph Heiss
2023-09-21 11:30 ` Thomas Lamprecht
2023-09-21 11:39 ` Christoph Heiss [this message]
2023-09-05 13:28 ` [pve-devel] [RFC installer 3/6] add answer file fetch script Aaron Lauterer
2023-09-20 9:52 ` Christoph Heiss
2023-09-05 13:28 ` [pve-devel] [PATCH installer 4/6] makefile: fix handling of multiple usr_bin files Aaron Lauterer
2023-09-05 13:28 ` [pve-devel] [RFC installer 5/6] makefile: add auto installer Aaron Lauterer
2023-09-05 13:28 ` [pve-devel] [RFC docs 6/6] installation: add unattended documentation 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=7pceqwz6s5zqrkkkaqww4plzhwgzgjsgxwfdjqj7hxwostkds3@hbaxjh7zdrjs \
--to=c.heiss@proxmox.com \
--cc=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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