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 05/10] pvestatd: sdn: adapt to changes in status reporting
Date: Thu, 13 Nov 2025 17:19:19 +0100	[thread overview]
Message-ID: <20251113161926.793020-17-s.hanreich@proxmox.com> (raw)
In-Reply-To: <20251113161926.793020-1-s.hanreich@proxmox.com>

Since pve-network now includes the fabric status in its top-level
status function call (SDN::status), move pvestatd over to use the
zone-specific function for generating SDN resources instead.
Additionally, the zone_type field has been added in the output of the
zone status, so broadcast and return that field as well. Main use-case
for now is discerning the type of zones, to decide which panels to
show in the SDN browser.

Also, the have_sdn guard can be removed since SDN is pre-installed and
therefore the guard is no longer needed.

Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
 PVE/API2/Cluster.pm     | 31 +++++++++++++++++++------------
 PVE/Service/pvestatd.pm | 16 ++++------------
 2 files changed, 23 insertions(+), 24 deletions(-)

diff --git a/PVE/API2/Cluster.pm b/PVE/API2/Cluster.pm
index eb9ddcc39..4f41a005c 100644
--- a/PVE/API2/Cluster.pm
+++ b/PVE/API2/Cluster.pm
@@ -469,6 +469,11 @@ __PACKAGE__->register_method({
                     enum => ["fabric", "zone"],
                     optional => 1,
                 },
+                'zone-type' => {
+                    description => "The type of an SDN zone (for type 'sdn').",
+                    type => "string",
+                    optional => 1,
+                },
                 protocol => {
                     description =>
                         "The protocol of a fabric (for type 'network', network-type 'fabric').",
@@ -638,18 +643,20 @@ __PACKAGE__->register_method({
 
                 my $sdns = decode_json($nodes->{$node});
 
-                    for my $id (sort keys %{$sdns}) {
-                        next if !$rpcenv->check($authuser, "/sdn/zones/$id", ['SDN.Audit'], 1);
-                        my $sdn = $sdns->{$id};
-                        my $entry = {
-                            id => "sdn/$node/$id",
-                            sdn => $id,
-                            node => $node,
-                            type => 'sdn',
-                            status => $sdn->{'status'},
-                        };
-                        push @$res, $entry;
-                    }
+                for my $id (sort keys %{$sdns}) {
+                    next if !$rpcenv->check($authuser, "/sdn/zones/$id", ['SDN.Audit'], 1);
+                    my $sdn = $sdns->{$id};
+                    my $entry = {
+                        id => "sdn/$node/$id",
+                        sdn => $id,
+                        node => $node,
+                        type => 'sdn',
+                        status => $sdn->{'status'},
+                    };
+
+                    $entry->{'zone-type'} = $sdn->{'zone-type'} if defined($sdn->{'zone-type'});
+
+                    push @$res, $entry;
                 }
             }
         }
diff --git a/PVE/Service/pvestatd.pm b/PVE/Service/pvestatd.pm
index 572eb7eb5..98d421f48 100755
--- a/PVE/Service/pvestatd.pm
+++ b/PVE/Service/pvestatd.pm
@@ -15,6 +15,7 @@ use PVE::CpuSet;
 use Filesys::Df;
 use PVE::INotify;
 use PVE::Network;
+use PVE::Network::SDN::Zones;
 use PVE::RS::SDN::Fabrics;
 use PVE::NodeConfig;
 use PVE::Cluster qw(cfs_read_file);
@@ -38,12 +39,6 @@ use PVE::Status::Plugin;
 
 use base qw(PVE::Daemon);
 
-my $have_sdn;
-eval {
-    require PVE::Network::SDN;
-    $have_sdn = 1;
-};
-
 my $opt_debug;
 my $restart_request;
 
@@ -767,13 +762,10 @@ sub update_ceph_metadata {
 }
 
 sub update_sdn_status {
+    my ($zone_status, $vnet_status) = PVE::Network::SDN::Zones::status();
 
-    if ($have_sdn) {
-        my ($transport_status, $vnet_status) = PVE::Network::SDN::status();
-
-        my $status = $transport_status ? encode_json($transport_status) : undef;
-        PVE::Cluster::broadcast_node_kv("sdn", $status);
-    }
+    my $status = $zone_status ? encode_json($zone_status) : undef;
+    PVE::Cluster::broadcast_node_kv("sdn", $status);
 }
 
 sub update_network_status {
-- 
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:25 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 ` Stefan Hanreich [this message]
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 ` [pve-devel] [PATCH pve-manager v4 10/10] ui: sdn: status view: adapt to new network resource Stefan Hanreich
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-17-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