From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pdm-devel@lists.proxmox.com
Subject: [pdm-devel] [PATCH proxmox{, -datacenter-manager} 0/8] Integration of IP-VRF and MAC-VRF status to EVPN panel
Date: Fri, 7 Nov 2025 09:59:20 +0100 [thread overview]
Message-ID: <20251107085934.118815-1-s.hanreich@proxmox.com> (raw)
This patch series requires the API endpoints introduced in the Proxmox VE patch
series [1] - in particular the zone/ip-vrf and the vnet/mac-vrf endpoints.
It adds a second panel to the EVPN view and makes it a split view similar to the
remote view. It utilizes the endpoints to display status information about
selected zones / vnets.
[1] https://lore.proxmox.com/pve-devel/20251107085553.113655-1-s.hanreich@proxmox.com/T/
proxmox:
Stefan Hanreich (3):
pve-api-types: add zone / vnet status reporting endpoints
pve-api-types: generate ip-vrf / mac-vrf endpoints
pve-api-types: regenerate
pve-api-types/generate.pl | 4 +
pve-api-types/pve-api.json | 286 ++++++++++++++++++++++++++-
pve-api-types/src/generated/code.rs | 25 +++
pve-api-types/src/generated/types.rs | 104 ++++++++--
4 files changed, 402 insertions(+), 17 deletions(-)
proxmox-datacenter-manager:
Stefan Hanreich (5):
server: api: sdn: add ip-vrf endpoint
server: api: sdn: add mac-vrf endpoint
ui: sdn: evpn: add zone status panel
ui: sdn: evpn: add vnet status panel
sdn: evpn: add detail panel to the evpn panel
lib/pdm-client/src/lib.rs | 23 +++
server/src/api/nodes/mod.rs | 2 +
server/src/api/nodes/sdn.rs | 101 +++++++++++++
server/src/api/pve/node.rs | 3 +-
ui/src/sdn/evpn/evpn_panel.rs | 129 ++++++++++++++--
ui/src/sdn/evpn/mod.rs | 36 +++++
ui/src/sdn/evpn/remote_tree.rs | 71 ++++++---
ui/src/sdn/evpn/vnet_status.rs | 253 ++++++++++++++++++++++++++++++++
ui/src/sdn/evpn/vrf_tree.rs | 29 +++-
ui/src/sdn/evpn/zone_status.rs | 261 +++++++++++++++++++++++++++++++++
10 files changed, 874 insertions(+), 34 deletions(-)
create mode 100644 server/src/api/nodes/sdn.rs
create mode 100644 ui/src/sdn/evpn/vnet_status.rs
create mode 100644 ui/src/sdn/evpn/zone_status.rs
Summary over all repositories:
14 files changed, 1276 insertions(+), 51 deletions(-)
--
Generated by git-murpp 0.8.0
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
next reply other threads:[~2025-11-07 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 8:59 Stefan Hanreich [this message]
2025-11-07 8:59 ` [pdm-devel] [PATCH proxmox 1/3] pve-api-types: add zone / vnet status reporting endpoints Stefan Hanreich
2025-11-07 8:59 ` [pdm-devel] [PATCH proxmox 2/3] pve-api-types: generate ip-vrf / mac-vrf endpoints Stefan Hanreich
2025-11-07 8:59 ` [pdm-devel] [PATCH proxmox 3/3] pve-api-types: regenerate Stefan Hanreich
2025-11-07 8:59 ` [pdm-devel] [PATCH proxmox-datacenter-manager 1/5] server: api: sdn: add ip-vrf endpoint Stefan Hanreich
2025-11-07 8:59 ` [pdm-devel] [PATCH proxmox-datacenter-manager 2/5] server: api: sdn: add mac-vrf endpoint Stefan Hanreich
2025-11-07 8:59 ` [pdm-devel] [PATCH proxmox-datacenter-manager 3/5] ui: sdn: evpn: add zone status panel Stefan Hanreich
2025-11-07 8:59 ` [pdm-devel] [PATCH proxmox-datacenter-manager 4/5] ui: sdn: evpn: add vnet " Stefan Hanreich
2025-11-07 8:59 ` [pdm-devel] [PATCH proxmox-datacenter-manager 5/5] sdn: evpn: add detail panel to the evpn panel 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=20251107085934.118815-1-s.hanreich@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=pdm-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