From: Kyle Schmitt <kyleaschmitt@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Any plans to migrate to systemd-networkd?
Date: Thu, 3 Oct 2024 17:10:45 -0500 [thread overview]
Message-ID: <CAO6gj48wmVVkKnAe1Yt3gpvfcZ+R+v7wcwovGvNYEmo1ud_e9w@mail.gmail.com> (raw)
In-Reply-To: <78619bca-8468-43e7-a67e-00f82f6c9cd7@gmail.com>
For an alternate point of view, unless does away with support for
everything other systemd-networkd, please don't change. Dealing with my
production systems, most of these systemd changes feel like change for
change's sake, not progress. And I haven't had pleasant experiences with
systemd-networkd in production environments.
On Thu, Sep 12, 2024 at 7:20 PM Uwe Sauter <uwe.sauter.de@gmail.com> wrote:
>
> Dear Proxmox team, hi all,
>
>
> I stumbled across an article over at lwn.net:
>
> ===
> Debating ifupdown replacements for Debian trixie
>
> Debian does not have an official way to configure networking. Instead, it
has four [1] recommended ways to configure
> networking, one of which is the venerable ifupdown [2], which has been
part of Debian since the turn of the century and
> is showing its age. A conversation about its maintainability and possible
replacement with ifupdown‑ng [3] has led to
> discussions about the default network-management tools for Debian
"trixie" [4] (Debian 13, which is expected in 2025)
> and beyond. No route to consensus has been found, yet.
> ===
> [1] https://wiki.debian.org/NetworkConfiguration
> [2] https://salsa.debian.org/debian/ifupdown
> [3] https://github.com/ifupdown-ng/ifupdown-ng
> [4] https://www.debian.org/releases/trixie/
>
>
> Having made good experiences with systemd-networkd on Debian, Rocky Linux
and Arch Linux I was wondering whether Proxmox
> is working towards using systemd-networkd as the configuration tool in
one of the next major versions?
>
>
> Best,
>
> Uwe
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next parent reply other threads:[~2024-10-03 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <78619bca-8468-43e7-a67e-00f82f6c9cd7@gmail.com>
2024-10-03 22:10 ` Kyle Schmitt [this message]
2024-10-03 23:03 ` John Crisp
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=CAO6gj48wmVVkKnAe1Yt3gpvfcZ+R+v7wcwovGvNYEmo1ud_e9w@mail.gmail.com \
--to=kyleaschmitt@gmail.com \
--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