public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Daniel Herzig <d.herzig@proxmox.com>
To: Hannes Laimer <h.laimer@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [pve-network 2/2] fix #7837: simpleplugin: make use of get_subnets_with_config
Date: Fri, 28 Aug 2026 10:41:41 +0200	[thread overview]
Message-ID: <87y0dq4oxm.fsf@proxmox.com> (raw)
In-Reply-To: <d5ff3825-3623-4e77-829e-f7e16518c543@proxmox.com>

Hannes Laimer <h.laimer@proxmox.com> writes:

> 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.
>

Agreed, apparently I was too deep in it so I missed adding the cover
letter. Absolutely makes sense, will be added in v2. I'll also look into
the call from the Evpnplugin module, thanks for the headsup!

>
> [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;




  reply	other threads:[~2026-08-28  8:41 UTC|newest]

Thread overview: 6+ 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
2026-08-28  8:41     ` Daniel Herzig [this message]
2026-08-27 13:58 ` [pve-network 1/2] vnets: introduce get_subnets_with_config Hannes Laimer
2026-08-28  8:35   ` Daniel Herzig

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=87y0dq4oxm.fsf@proxmox.com \
    --to=d.herzig@proxmox.com \
    --cc=h.laimer@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