public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Alex Harvey <alexharv074@gmail.com>
To: pve-devel@lists.proxmox.com
Subject: [RFC] PVE installer: GRUB PXE and Foreman/Satellite integration
Date: Sun, 30 Aug 2026 17:35:41 +1000	[thread overview]
Message-ID: <CAF0Ep4X6N=Dx79VyugFtwEpo8M49uihjrypcLyaH=V5H21Jseg@mail.gmail.com> (raw)

Hi all,

I am working on automated Proxmox VE installation in an environment managed
by Foreman / Red Hat Satellite.

The current POC uses Satellite for DHCP, TFTP and iPXE provisioning. It
requires two workarounds:

* A custom answer adapter translates the installer’s HTTP POST into
  Foreman’s /unattended/provision?mac=<MAC> request.
* iPXE supplies the prepared ISO as an initrd. This works there, but is not
  suitable as the basis for reliable GRUB PXE boot with a production-sized
ISO.

Note also that support for iPXE is deprecated in Satellite.

I opened these related enhancement requests:

* https://bugzilla.proxmox.com/show_bug.cgi?id=7990
  GRUB PXE installation media without loading the full ISO as an initrd
* https://bugzilla.proxmox.com/show_bug.cgi?id=7991
  Generate GRUB PXE configuration from proxmox-auto-install-assistant
* https://bugzilla.proxmox.com/show_bug.cgi?id=7992
  Native answer-file retrieval from Foreman/Satellite

Before attempting patches, I would appreciate guidance and feedback on the
proposed
design:

1. Would support for `--pxe-loader grub` be welcome?
2. If so, would there be a preferred way for a GRUB PXE boot to provide the
prepared
   installation medium without GRUB loading the full ISO as an initrd?
3. Would a Foreman-compatible answer file fetch mode, using the
provisioning NIC
   MAC to retrieve a host-specific answer file, be acceptable?

Many thanks,
Alex Harvey

                 reply	other threads:[~2026-09-02  8:32 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='CAF0Ep4X6N=Dx79VyugFtwEpo8M49uihjrypcLyaH=V5H21Jseg@mail.gmail.com' \
    --to=alexharv074@gmail.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal