public inbox for pdm-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Christoph Heiss" <c.heiss@proxmox.com>
To: "Lukas Wagner" <l.wagner@proxmox.com>
Cc: Proxmox Datacenter Manager development discussion
	<pdm-devel@lists.proxmox.com>
Subject: Re: [pdm-devel] [PATCH proxmox/datacenter-manager 00/13] initial auto-installer integration
Date: Thu, 04 Dec 2025 16:06:05 +0100	[thread overview]
Message-ID: <DEPIXER0QRJK.3B13ADZ3XS6AY@proxmox.com> (raw)
In-Reply-To: <DEPHWEJKLI1W.1STZHWCK10P0H@proxmox.com>

On Thu Dec 4, 2025 at 3:17 PM CET, Lukas Wagner wrote:
> On Thu Dec 4, 2025 at 1:51 PM CET, Christoph Heiss wrote:
>> This series adds integration with our automated installer [0] for all our
>> products. With this, Proxmox Datacenter Manager can be used for serving
>> answer files via HTTP(S) in an automated fashion.
>>
>> It provides two new panels:
>>
>> - Automated Installations: List all past and currently ongoing
>>   installations.
>> - Prepared Answers: Enables users to do the whole CRUD cycle for
>>   prepared answers, i.e. create new answers (from scratch or based on
>>   existing ones), edit and delete.
>>
>> Permission-wise, everything is currently scoped on
>> /system/auto-installation.
>>
>> UI
>> ==
>>
>> Happy about feedback regarding the UI, especially the editing dialog! By
>> the nature of it, the auto-installer has a lot more options than the
>> standard GUI/TUI installer, and it's kind of hard to not fully cramp up
>> the UI while still providing all options.
>>
>> TOML API
>> ========
>>
>> The auto-installer (currently) only supports TOML as input format for
>> the answer, so we need to hack around a bit to serve TOML in the API.
>> This is done in patch #12, by implementing the api method
>> directly.
>>
>> Serving TOML from an endpoint under /api2/json/ obviously is rather
>> wrong, so I'm definitely open for suggestions.
>> We probably also don't want to implement `/api2/toml/` if I'd have to
>> guess (or would that be possible selectively, i.e. just for this one
>> endpoint?).
>>
>> Adding JSON support to proxmox-fetch-answer is on my list, but this
>> would still be needed if we want to keep compatibility with older ISOs.
>>
>
> Cool stuff, I didn't even know that somebody was working on this!
>
> Couldn't really try it out, I think there is some issue in the patches
> that you've posted. I'm getting a 'unresolved import
> `proxmox_installer_types::answer::fetch::AnswerFetchResponse' error when
> trying to compile PDM. Checking the code in the installer-types crate, I
> also couldn't find a type like this - could you cross-check?

Thanks for the report, and sorry!

Yeah, definitely a mistake on my end - some leftover "gunk" from an
earlier iteration I had still lying around (for later usage with the
wait-mechanism). I'll send a v2 shortly!

>
> Thanks!



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


  reply	other threads:[~2025-12-04 15:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 12:51 Christoph Heiss
2025-12-04 12:51 ` [pdm-devel] [PATCH proxmox 01/13] api-macro: allow $ in identifier name Christoph Heiss
2025-12-04 12:51 ` [pdm-devel] [PATCH proxmox 02/13] network-types: move `Fqdn` type from proxmox-installer-common Christoph Heiss
2025-12-04 12:51 ` [pdm-devel] [PATCH proxmox 03/13] network-types: implement api type for Fqdn Christoph Heiss
2025-12-04 12:51 ` [pdm-devel] [PATCH proxmox 04/13] network-types: add api wrapper type for std::net::IpAddr Christoph Heiss
2025-12-04 12:51 ` [pdm-devel] [PATCH proxmox 05/13] installer-types: add common types used by the installer Christoph Heiss
2025-12-04 12:51 ` [pdm-devel] [PATCH proxmox 06/13] installer-types: add types used by the auto-installer Christoph Heiss
2025-12-04 12:51 ` [pdm-devel] [PATCH proxmox 07/13] installer-types: implement api type for all externally-used types Christoph Heiss
2025-12-04 12:51 ` [pdm-devel] [PATCH datacenter-manager 08/13] api-types: add api types for auto-installer integration Christoph Heiss
2025-12-04 12:51 ` [pdm-devel] [PATCH datacenter-manager 09/13] config: add auto-installer configuration module Christoph Heiss
2025-12-04 12:51 ` [pdm-devel] [PATCH datacenter-manager 10/13] acl: wire up new /system/auto-installation acl path Christoph Heiss
2025-12-04 12:51 ` [pdm-devel] [PATCH datacenter-manager 11/13] server: api: add auto-installer integration module Christoph Heiss
2025-12-04 12:51 ` [pdm-devel] [PATCH datacenter-manager 12/13] ui: auto-installer: add installations overview panel Christoph Heiss
2025-12-04 12:51 ` [pdm-devel] [PATCH datacenter-manager 13/13] ui: auto-installer: add prepared answer configuration panel Christoph Heiss
2025-12-04 14:17 ` [pdm-devel] [PATCH proxmox/datacenter-manager 00/13] initial auto-installer integration Lukas Wagner
2025-12-04 15:06   ` Christoph Heiss [this message]
2025-12-05 11:26 ` Christoph Heiss

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=DEPIXER0QRJK.3B13ADZ3XS6AY@proxmox.com \
    --to=c.heiss@proxmox.com \
    --cc=l.wagner@proxmox.com \
    --cc=pdm-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal