From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-manager 1/1] sdn: add dry-run view for sdn apply
Date: Tue, 24 Feb 2026 13:49:45 +0100 [thread overview]
Message-ID: <f9fadb5a-d800-42fd-b680-98615dd9a95b@proxmox.com> (raw)
In-Reply-To: <20260203160246.353351-23-g.goller@proxmox.com>
The panel is still a bit barebones imo, the diff should at least be in a
monospaced font. Colored output would be better, side-by-side comparison
really great. I don't think we have anything like that in our ExtJS
widget toolkit though - so this would have to be implemented from
scratch. Maybe @Dominik as ideas / thoughts on that?
On 2/3/26 5:03 PM, Gabriel Goller wrote:
> Introduce a new SdnDiffView modal that runs a dry-run and shows the frr
> configuration changes which will be made when clicking apply. Now the
> user knows which frr config options will be set without needing to apply
> the config.
>
> Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
> ---
> www/manager6/Makefile | 1 +
> www/manager6/sdn/SdnDiffView.js | 123 ++++++++++++++++++++++++++++++++
> www/manager6/sdn/StatusView.js | 8 +++
> 3 files changed, 132 insertions(+)
> create mode 100644 www/manager6/sdn/SdnDiffView.js
>
> diff --git a/www/manager6/Makefile b/www/manager6/Makefile
> index 4558d53e54be..da602523b27a 100644
> --- a/www/manager6/Makefile
> +++ b/www/manager6/Makefile
> @@ -286,6 +286,7 @@ JSSRC= \
> sdn/ControllerView.js \
> sdn/Status.js \
> sdn/StatusView.js \
> + sdn/SdnDiffView.js \
> sdn/VnetEdit.js \
> sdn/VnetView.js \
> sdn/VnetACLView.js \
> diff --git a/www/manager6/sdn/SdnDiffView.js b/www/manager6/sdn/SdnDiffView.js
> new file mode 100644
> index 000000000000..2de10efd14b6
> --- /dev/null
> +++ b/www/manager6/sdn/SdnDiffView.js
> @@ -0,0 +1,123 @@
> +Ext.define('PVE.sdn.SdnDiffView', {
> + extend: 'Ext.window.Window',
> +
> + maxWidth: 1000,
> + maxHeight: 1000,
> + minWidth: 600,
> + minHeight: 400,
> + scrollable: true,
> + modal: true,
> + title: gettext('FRR config diff view'),
Potentially improve the title here, sounds a bit half-baked imo.
'Pending FRR [configuration] changes' or something like that? Or 'FRR
configuration preview'. Some combination of Pending / Preview and FRR
configuration...
> +
> + node: undefined,
> +
> + viewModel: {
> + data: {
> + diff: undefined,
> + },
> + },
> +
> + items: [
> + {
> + xtype: 'displayfield',
> + padding: 10,
> + scrollable: true,
> + bind: {
> + value: '{diff}',
> + },
> + },
> + ],
> + buttons: [
> + {
> + handler: function () {
> + this.up('window').close();
> + },
> + text: gettext('OK'),
'OK' might give the impression to some users that the config will be
applied when pressing the button - maybe close is better here?
> + },
> + ],
> +
> + loadDiff: async function () {
> + let me = this;
> +
> + let req = await Proxmox.Async.api2({
> + url: `/cluster/sdn/dry-apply`,
> + params: { node: me.node },
> + method: 'PUT',
> + });
> +
> + return req.result.data;
> + },
> +
> + load: function () {
> + let me = this;
> +
> + me.setLoading('fetching node diff');
> +
> + me.loadDiff()
> + .catch(Proxmox.Utils.alertResponseFailure)
> + .then((diff) => {
> + if (diff['frr-diff'] === null) {
> + this.getViewModel().set('diff', '');
> + } else {
> + this.getViewModel().set('diff', diff['frr-diff'].replaceAll('\n', '<br>'));
potentially use a <pre> tag and escape the returned config instead of
replacing new lines with a <br>?
> + }
> + })
> + .finally(() => {
> + me.setLoading(false);
> + });
> + },
> +
> + getNodeSelector: function () {
> + let me = this;
> +
> + return Ext.create('PVE.form.NodeSelector', {
> + xtype: 'pveNodeSelector',
> + reference: 'nodeselector',
> + fieldLabel: gettext('Node'),
> + padding: 10,
> + labelWidth: 120,
> + name: 'node',
> + allowBlank: false,
> + listeners: {
> + change: function (f, value) {
> + me.node = value;
> + me.load();
> + },
> + },
> + listConfig: {
> + columns: [
> + {
> + header: gettext('Node'),
> + dataIndex: 'node',
> + sortable: true,
> + hideable: false,
> + flex: 1,
> + },
> + ],
> + },
> + store: {
> + fields: ['node'],
> + proxy: {
> + type: 'proxmox',
> + url: '/api2/json/nodes',
> + },
> + sorters: [
> + {
> + property: 'node',
> + direction: 'ASC',
> + },
> + ],
> + },
> + });
> + },
> +
> + initComponent: function () {
> + let me = this;
> +
> + me.nodeSelector = me.getNodeSelector();
> +
> + me.items = [me.nodeSelector, ...me.items];
> +
> + me.callParent();
> + },
> +});
> diff --git a/www/manager6/sdn/StatusView.js b/www/manager6/sdn/StatusView.js
> index fbc712c6cf6b..fada50411e91 100644
> --- a/www/manager6/sdn/StatusView.js
> +++ b/www/manager6/sdn/StatusView.js
> @@ -69,6 +69,14 @@ Ext.define(
> });
> },
> },
> + {
> + text: gettext('Dry-Run'),
Dry-run might be misleading as well, since currently it is limited to
the FRR configuration only. Although it might not be too hard to extend
this to ifupdown2 - maybe that could be an additional quick win as
follow-up?
That reminds me, that we should also implement rolling back of pending
changes (and potentially previewing the changes there as well) in the UI
- this would play quite nicely with this addition...
> + handler: function () {
> + Ext.create('PVE.sdn.SdnDiffView', {
> + autoShow: true,
> + });
> + },
> + },
> ],
> viewConfig: {
> trackOver: false,
next prev parent reply other threads:[~2026-02-24 12:48 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
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 [this message]
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=f9fadb5a-d800-42fd-b680-98615dd9a95b@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