From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH installer 0/6] fix #5811: add option to retrieve FQDN from DHCP configuration
Date: Thu, 27 Mar 2025 16:17:11 +0100 [thread overview]
Message-ID: <20250327151718.1084841-1-c.heiss@proxmox.com> (raw)
Fixes #5811 [0].
Adds a new option to the answer file for specifying to use the
DHCP-provided hostname and domain. For the domain, an additional
fallback/default can be specified, in case the DHCP server only provides
hostnames. The hostname is always required in this mode.
The addition to the answer file format is done in a backwards-compatible
way.
Users can now specify the following to use the DHCP-provided domain:
```
[global]
fqdn.source = "from-dhcp"
```
or additionally with a custom domain:
```
[global.fqdn]
source = "from-dhcp"
domain = "custom.domain.local"
```
Patches #1 through #4 can all be applied independently, #1 & #4 are pure
cleanups.
[0] https://bugzilla.proxmox.com/show_bug.cgi?id=5811
Diffstat
========
Christoph Heiss (6):
auto: utils: avoid a force unwrap()
auto: tests: parse-answer: allow per-test runtime env
auto: tests: allow testing for serde parse errors of answer files
tui, common: move network option tests to correct crate
common: options: allow user-supplied domain for network options
fix #5811: auto: add option to retrieve FQDN from DHCP configuration
proxmox-auto-installer/src/answer.rs | 36 +++-
proxmox-auto-installer/src/utils.rs | 43 ++++-
proxmox-auto-installer/tests/parse-answer.rs | 43 +++--
.../parse_answer/fqdn_from_dhcp.json | 19 ++
.../parse_answer/fqdn_from_dhcp.toml | 14 ++
...cp_no_dhcp_domain_with_default_domain.json | 19 ++
...cp_no_dhcp_domain_with_default_domain.toml | 17 ++
...ll_fqdn_from_dhcp_with_default_domain.json | 19 ++
...ll_fqdn_from_dhcp_with_default_domain.toml | 17 ++
.../fqdn_from_dhcp_no_default_domain.json | 3 +
...n_from_dhcp_no_default_domain.run-env.json | 1 +
.../fqdn_from_dhcp_no_default_domain.toml | 14 ++
.../parse_answer_fail/fqdn_hostname_only.json | 3 +
.../parse_answer_fail/fqdn_hostname_only.toml | 14 ++
.../parse_answer_fail/no_fqdn_from_dhcp.json | 3 +
.../no_fqdn_from_dhcp.run-env.json | 1 +
.../parse_answer_fail/no_fqdn_from_dhcp.toml | 14 ++
.../tests/resources/run-env-info.json | 2 +-
proxmox-installer-common/Cargo.toml | 3 +
proxmox-installer-common/src/options.rs | 165 +++++++++++++++++-
proxmox-post-hook/src/main.rs | 19 +-
proxmox-tui-installer/Cargo.toml | 3 -
proxmox-tui-installer/src/main.rs | 2 +-
proxmox-tui-installer/src/options.rs | 93 ----------
24 files changed, 440 insertions(+), 127 deletions(-)
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer/fqdn_from_dhcp.json
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer/fqdn_from_dhcp.toml
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer/fqdn_from_dhcp_no_dhcp_domain_with_default_domain.json
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer/fqdn_from_dhcp_no_dhcp_domain_with_default_domain.toml
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer/full_fqdn_from_dhcp_with_default_domain.json
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer/full_fqdn_from_dhcp_with_default_domain.toml
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer_fail/fqdn_from_dhcp_no_default_domain.json
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer_fail/fqdn_from_dhcp_no_default_domain.run-env.json
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer_fail/fqdn_from_dhcp_no_default_domain.toml
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer_fail/fqdn_hostname_only.json
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer_fail/fqdn_hostname_only.toml
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer_fail/no_fqdn_from_dhcp.json
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer_fail/no_fqdn_from_dhcp.run-env.json
create mode 100644 proxmox-auto-installer/tests/resources/parse_answer_fail/no_fqdn_from_dhcp.toml
--
2.48.1
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-03-27 15:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 15:17 Christoph Heiss [this message]
2025-03-27 15:17 ` [pve-devel] [PATCH installer 1/6] auto: utils: avoid a force unwrap() Christoph Heiss
2025-04-04 12:51 ` [pve-devel] applied: " Thomas Lamprecht
2025-03-27 15:17 ` [pve-devel] [PATCH installer 2/6] auto: tests: parse-answer: allow per-test runtime env Christoph Heiss
2025-04-04 12:51 ` [pve-devel] applied: " Thomas Lamprecht
2025-03-27 15:17 ` [pve-devel] [PATCH installer 3/6] auto: tests: allow testing for serde parse errors of answer files Christoph Heiss
2025-04-04 12:51 ` [pve-devel] applied: " Thomas Lamprecht
2025-03-27 15:17 ` [pve-devel] [PATCH installer 4/6] tui, common: move network option tests to correct crate Christoph Heiss
2025-04-04 12:54 ` Thomas Lamprecht
2025-03-27 15:17 ` [pve-devel] [PATCH installer 5/6] common: options: allow user-supplied domain for network options Christoph Heiss
2025-03-27 15:17 ` [pve-devel] [PATCH installer 6/6] fix #5811: auto: add option to retrieve FQDN from DHCP configuration Christoph Heiss
2025-04-01 13:15 ` Daniel Kral
2025-04-01 13:25 ` Christoph Heiss
2025-04-01 13:29 ` Stefan Hanreich
2025-04-01 13:44 ` Daniel Kral
2025-04-01 14:58 ` Thomas Lamprecht
2025-04-01 13:45 ` [pve-devel] [PATCH installer 0/6] fix #5811: " Daniel Kral
2025-04-01 14:05 ` 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=20250327151718.1084841-1-c.heiss@proxmox.com \
--to=c.heiss@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal