public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-manager v4 10/10] ui: sdn: status view: adapt to new network resource
Date: Thu, 13 Nov 2025 17:19:24 +0100	[thread overview]
Message-ID: <20251113161926.793020-22-s.hanreich@proxmox.com> (raw)
In-Reply-To: <20251113161926.793020-1-s.hanreich@proxmox.com>

Adapt the SDN status overview to use the new network resource over the
old SDN resource type. Also display the network_type field in addition
to the existing fields - so users can discern between different types
of network entities.

Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
 www/manager6/sdn/StatusView.js | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/www/manager6/sdn/StatusView.js b/www/manager6/sdn/StatusView.js
index dd05c73fd..fbc712c6c 100644
--- a/www/manager6/sdn/StatusView.js
+++ b/www/manager6/sdn/StatusView.js
@@ -33,7 +33,7 @@ Ext.define(
                 ],
                 filters: {
                     property: 'type',
-                    value: 'sdn',
+                    value: 'network',
                     operator: '==',
                 },
             });
@@ -77,13 +77,18 @@ Ext.define(
                     {
                         header: 'SDN',
                         width: 80,
-                        dataIndex: 'sdn',
+                        dataIndex: 'network',
                     },
                     {
                         header: gettext('Node'),
                         width: 80,
                         dataIndex: 'node',
                     },
+                    {
+                        header: gettext('Type'),
+                        width: 80,
+                        dataIndex: 'network-type',
+                    },
                     {
                         header: gettext('Status'),
                         width: 80,
@@ -102,7 +107,7 @@ Ext.define(
     function () {
         Ext.define('pve-sdn-status', {
             extend: 'Ext.data.Model',
-            fields: ['id', 'type', 'node', 'status', 'sdn'],
+            fields: ['id', 'type', 'node', 'status', 'network'],
             idProperty: 'id',
         });
     },
-- 
2.47.3


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  parent reply	other threads:[~2025-11-13 16:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 16:19 [pve-devel] [PATCH manager/network/proxmox-perl-rs v4 00/21] Improve status reporting for SDN / networking Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH proxmox-perl-rs v4 1/2] pve-rs: update proxmox-frr dependency Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH proxmox-perl-rs v4 2/2] pve-rs: sdn status: rename network_type to network-type Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-network v4 1/9] refactor: rework api module structure for the /nodes/{node}/sdn subdir Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-network v4 2/9] fabrics: add fabrics status to SDN::status function Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-network v4 3/9] sdn: status: add zone type to sdn resource Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-network v4 4/9] api: nodes: fabrics: add endpoint for querying route status Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-network v4 5/9] api: nodes: fabrics: add endpoint for querying neighbor information Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-network v4 6/9] api: nodes: fabrics: add endpoint for querying interface status Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-network v4 7/9] api: nodes: zones: add bridge status Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-network v4 8/9] api: nodes: zones: add ip vrf endpoint for evpn zones Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-network v4 9/9] api: nodes: vnets: add mac-vrf endpoint for evpn vnets Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-manager v4 01/10] api: nodes: use new status module for sdn subdirectory Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-manager v4 02/10] refactor: ui: sdn browser: parametrize zone content panel Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-manager v4 03/10] pvestatd: add network resource to status reporting Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-manager v4 04/10] api: cluster: add support for network resource type Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-manager v4 05/10] pvestatd: sdn: adapt to changes in status reporting Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-manager v4 06/10] ui: resource tree: add network resource Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-manager v4 07/10] ui: network browser: Add ip-vrf panel for evpn zones Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-manager v4 08/10] ui: network browser: add mac vrf panel Stefan Hanreich
2025-11-13 16:19 ` [pve-devel] [PATCH pve-manager v4 09/10] ui: network browser: add zone bridge view Stefan Hanreich
2025-11-13 16:19 ` Stefan Hanreich [this message]
2025-11-14  1:07 ` [pve-devel] applied: [PATCH manager/network/proxmox-perl-rs v4 00/21] Improve status reporting for SDN / networking Thomas Lamprecht

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=20251113161926.793020-22-s.hanreich@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal