From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-network 09/10] api: add dry-run endpoint for sdn apply to preview changes
Date: Tue, 24 Feb 2026 14:53:20 +0100 [thread overview]
Message-ID: <146810ff-7103-4da0-a921-d1c570dc68e7@proxmox.com> (raw)
In-Reply-To: <20260203160246.353351-21-g.goller@proxmox.com>
Another idea, related to the comments already sent in pve-manager: We
could potentially return the output in a similar way to how the tests dp
it (using Tests::Difference) and then show this verbatim in the UI?
Of course, having a native diff viewer in the UI that can render diffs
would be preferable, but that seems a bit unrealistic considering that
we would like to roll this out relatively soon and if we're returning
raw diff outputs anyway, we could opt for a flavor that's a bit more
human-readable?
On 2/3/26 5:04 PM, Gabriel Goller wrote:
> Allows users to see the diff of frr configuration before applying
> SDN changes. Previously this was not possible and the user had to apply
> and then see what changed. Ideally this would also include the ifupdown2
> config, but that's a bit tricky since we add config lines in perl-rs as
> well.
>
> Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
> ---
> src/PVE/API2/Network/SDN.pm | 67 +++++++++++++++++++++++++++++++++++++
> src/PVE/Network/SDN.pm | 9 +++--
> 2 files changed, 74 insertions(+), 2 deletions(-)
>
> diff --git a/src/PVE/API2/Network/SDN.pm b/src/PVE/API2/Network/SDN.pm
> index b35a588d391d..9208d6f4e8b3 100644
> --- a/src/PVE/API2/Network/SDN.pm
> +++ b/src/PVE/API2/Network/SDN.pm
> @@ -3,6 +3,9 @@ package PVE::API2::Network::SDN;
> use strict;
> use warnings;
>
> +use File::Temp qw(tempfile);
There's a wrapper PVE::File::tempfile(_contents) which we should
probably use instead?
> +use Encode qw(decode);
> +
> use PVE::Cluster qw(cfs_lock_file cfs_read_file cfs_write_file);
> use PVE::Exception qw(raise_param_exc);
> use PVE::JSONSchema qw(get_standard_option);
> @@ -325,4 +328,68 @@ __PACKAGE__->register_method({
> },
> });
>
> +sub get_diff {
> + my ($filename_one, $filename_two) = @_;
> +
> + my $diff = '';
> +
> + my $cmd = ['/usr/bin/diff', '-b', '-N', '-u', $filename_one, $filename_two];
> + PVE::Tools::run_command(
> + $cmd,
> + noerr => 1,
> + outfunc => sub {
> + my ($line) = @_;
> + $diff .= decode('UTF-8', $line) . "\n";
> + },
> + );
> +
> + $diff = undef if !$diff;
> +
> + return $diff;
> +}
> +
> +__PACKAGE__->register_method({
> + name => 'dry-apply',
> + path => 'dry-apply',
We refer to the action as dry-run everywhere but the path is actually
'dry-apply'? I think dry-run would fit better.
> + method => 'PUT',
> + permissions => {
> + check => ['perm', '/nodes/{node}', ['Sys.Modify']],
> + },
> + description => "Dry-Run the SDN apply",
make this more descriptive?
> + protected => 1,
> + proxyto => 'node',
> + parameters => {
> + additionalProperties => 0,
> + properties => {
> + node => get_standard_option('pve-node'),
> + },
> + },
> +
> + returns => {
> + type => 'object',
> + properties => {
> + "frr-diff" =>
> + { type => 'string', description => 'The frr config generated by SDN.' },
description is kinda wrong? It's the difference/changes in the FRR
configuration - not the config itself.
> + },
> + },
> + code => sub {
> + my ($param) = @_;
> +
> + my $config = PVE::Network::SDN::compile_running_cfg();
> +
> + my $fabric_config = PVE::Network::SDN::Fabrics::config(0);
> + my $frr_config = PVE::Network::SDN::generate_frr_raw_config($config, $fabric_config);
> + my $new_config_frr = PVE::Network::SDN::Frr::raw_config_to_string($frr_config);
> +
> + my ($frr_tmp_fh, $frr_tmp_filename) = tempfile();
see above comment regarding PVE::File::tempfile
> + print $frr_tmp_fh $new_config_frr;
> +
> + my $return_value = {};
> + $return_value->{"frr-diff"} = get_diff('/etc/frr/frr.conf', $frr_tmp_filename);
> +
> + close($frr_tmp_fh);
> + return $return_value;
> + },
> +});
> +
> 1;
> diff --git a/src/PVE/Network/SDN.pm b/src/PVE/Network/SDN.pm
> index c000bed498ec..18938d73ba70 100644
> --- a/src/PVE/Network/SDN.pm
> +++ b/src/PVE/Network/SDN.pm
> @@ -187,8 +187,7 @@ sub pending_config {
>
> }
>
> -sub commit_config {
> -
> +sub compile_running_cfg {
> my $cfg = cfs_read_file($running_cfg);
> my $version = $cfg->{version};
>
> @@ -219,6 +218,12 @@ sub commit_config {
> fabrics => $fabrics,
> };
>
> + return $cfg;
> +}
> +
> +sub commit_config {
> + my $cfg = compile_running_cfg();
> +
> cfs_write_file($running_cfg, $cfg);
> }
>
next prev parent reply other threads:[~2026-02-24 13:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 16:01 [PATCH docs/manager/network/proxmox{-ve-rs,-perl-rs} 00/23] Generate frr config using jinja templates and rust types Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 1/9] ve-config: firewall: cargo fmt Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 2/9] frr: add proxmox-frr-templates package that contains templates Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 3/9] ve-config: remove FrrConfigBuilder struct Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 4/9] sdn-types: support variable-length NET identifier Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 5/9] frr: add template serializer and serialize fabrics using templates Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 6/9] frr: add isis configuration and templates Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 7/9] frr: support custom frr configuration lines Gabriel Goller
2026-02-19 12:17 ` Hannes Laimer
2026-02-19 15:01 ` Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 8/9] frr: add bgp support with templates and serialization Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-ve-rs 9/9] frr: store frr template content as a const map Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-perl-rs 1/2] sdn: add function to generate the frr config for all daemons Gabriel Goller
2026-02-03 16:01 ` [PATCH proxmox-perl-rs 2/2] sdn: add method to get a frr template Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 01/10] sdn: remove duplicate comment line '!' in frr config Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 02/10] sdn: tests: add missing comment " Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 03/10] tests: use Test::Differences to make test assertions Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 04/10] sdn: write structured frr config that can be rendered using templates Gabriel Goller
2026-02-19 13:52 ` Hannes Laimer
2026-02-19 15:36 ` Gabriel Goller
2026-02-19 15:44 ` Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 05/10] tests: rearrange some statements in the frr config Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 06/10] sdn: adjust frr.conf.local merging to rust template types Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 07/10] cli: add pvesdn cli tool for managing frr template overrides Gabriel Goller
2026-02-19 12:39 ` Hannes Laimer
2026-02-19 15:49 ` Gabriel Goller
2026-02-24 14:05 ` Stefan Hanreich
2026-02-03 16:01 ` [PATCH pve-network 08/10] debian: handle user modifications to FRR templates via ucf Gabriel Goller
2026-02-03 16:01 ` [PATCH pve-network 09/10] api: add dry-run endpoint for sdn apply to preview changes Gabriel Goller
2026-02-24 13:53 ` Stefan Hanreich [this message]
2026-02-03 16:01 ` [PATCH pve-network 10/10] test: add test for frr.conf.local merging Gabriel Goller
2026-02-24 13:27 ` Stefan Hanreich
2026-02-03 16:01 ` [PATCH pve-manager 1/1] sdn: add dry-run view for sdn apply Gabriel Goller
2026-02-24 12:49 ` Stefan Hanreich
2026-02-03 16:01 ` [PATCH pve-docs 1/1] docs: add man page for the `pvesdn` cli Gabriel Goller
2026-02-23 16:09 ` [PATCH docs/manager/network/proxmox{-ve-rs,-perl-rs} 00/23] Generate frr config using jinja templates and rust types Hannes Laimer
2026-02-24 11:09 ` Stefan Hanreich
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=146810ff-7103-4da0-a921-d1c570dc68e7@proxmox.com \
--to=s.hanreich@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