From: Hannes Laimer <h.laimer@proxmox.com>
To: Daniel Herzig <d.herzig@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [pve-network 2/2] fix #7837: simpleplugin: make use of get_subnets_with_config
Date: Thu, 27 Aug 2026 15:56:52 +0200 [thread overview]
Message-ID: <d5ff3825-3623-4e77-829e-f7e16518c543@proxmox.com> (raw)
In-Reply-To: <20260826154318.618730-2-d.herzig@proxmox.com>
Generally this LGTM! EVPN has the same problem[1], so fixing it
there as well would make sense for this series.
Aside from that, for more than one patch a `--cover-letter` would be
nice, that simplifies answering. Also allows to add some extra context
if needed.
nit: the commit messages mostly describe what the code does, ideally
they would include more of the _why_, something like:
```
Subnets were read from the running config instead of the one passed in,
so callers that generate without committing first, like the dry-run,
never saw pending subnet changes in the result.
```
for the commit that mentions the bugzilla issue.
[1]
https://git.proxmox.com/?p=pve-network.git;a=blob;f=src/PVE/Network/SDN/Zones/EvpnPlugin.pm;h=0e79707c374609f2505d842f99633e6311794f15;hb=refs/heads/master#l242
On 2026-08-26 17:43, Daniel Herzig wrote:
> At the given point we already have the subnet configuration by hand, so
> make sure to use it, instead of inherently falling back to
> re-reading '/etc/pve/sdn/.running-config'.
>
> Signed-off-by: Daniel Herzig <d.herzig@proxmox.com>
> ---
> src/PVE/Network/SDN/Zones/SimplePlugin.pm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/PVE/Network/SDN/Zones/SimplePlugin.pm b/src/PVE/Network/SDN/Zones/SimplePlugin.pm
> index 347eee9..d922035 100644
> --- a/src/PVE/Network/SDN/Zones/SimplePlugin.pm
> +++ b/src/PVE/Network/SDN/Zones/SimplePlugin.pm
> @@ -75,7 +75,7 @@ sub generate_sdn_config {
> my @iface_config = ();
>
> my $address = {};
> - my $subnets = PVE::Network::SDN::Vnets::get_subnets($vnetid, 1);
> + my $subnets = PVE::Network::SDN::Vnets::get_subnets_with_config($vnetid, $subnet_cfg);
>
> my $ipv4 = undef;
> my $ipv6 = undef;
next prev parent reply other threads:[~2026-08-27 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 15:43 [pve-network 1/2] vnets: introduce get_subnets_with_config Daniel Herzig
2026-08-26 15:43 ` [pve-network 2/2] fix #7837: simpleplugin: make use of get_subnets_with_config Daniel Herzig
2026-08-27 13:56 ` Hannes Laimer [this message]
2026-08-27 13:58 ` [pve-network 1/2] vnets: introduce get_subnets_with_config Hannes Laimer
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=d5ff3825-3623-4e77-829e-f7e16518c543@proxmox.com \
--to=h.laimer@proxmox.com \
--cc=d.herzig@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.