From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-network v4 8/9] api: nodes: zones: add ip vrf endpoint for evpn zones
Date: Thu, 13 Nov 2025 17:19:13 +0100 [thread overview]
Message-ID: <20251113161926.793020-11-s.hanreich@proxmox.com> (raw)
In-Reply-To: <20251113161926.793020-1-s.hanreich@proxmox.com>
This endpoint returns the state of the routing table on a node for a
given EVPN zone. This is used by the SDN browser panel to display
status information in the UI.
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
src/PVE/API2/Network/SDN/Nodes/Zone.pm | 79 ++++++++++++++++++++++++++
1 file changed, 79 insertions(+)
diff --git a/src/PVE/API2/Network/SDN/Nodes/Zone.pm b/src/PVE/API2/Network/SDN/Nodes/Zone.pm
index d7312df..43acbe9 100644
--- a/src/PVE/API2/Network/SDN/Nodes/Zone.pm
+++ b/src/PVE/API2/Network/SDN/Nodes/Zone.pm
@@ -297,4 +297,83 @@ __PACKAGE__->register_method({
},
});
+__PACKAGE__->register_method({
+ name => 'ip-vrf',
+ path => 'ip-vrf',
+ proxyto => 'node',
+ method => 'GET',
+ protected => 1,
+ description => "Get the IP VRF of an EVPN zone.",
+ permissions => {
+ check => ['perm', '/sdn/zones/{zone}', ['SDN.Audit']],
+ },
+ parameters => {
+ additionalProperties => 0,
+ properties => {
+ zone => {
+ type => 'string',
+ description => 'Name of an EVPN zone.',
+ },
+ node => get_standard_option('pve-node'),
+ },
+ },
+ returns => {
+ description => 'All entries in the VRF table of zone {zone} of the node.'
+ . 'This does not include /32 routes for guests on this host,'
+ . 'since they are handled via the respective vnet bridge directly.',
+ type => 'array',
+ items => {
+ type => 'object',
+ properties => {
+ ip => {
+ type => 'string',
+ format => 'CIDR',
+ description => 'The CIDR of the route table entry.',
+ },
+ metric => {
+ type => 'integer',
+ description => 'This route\'s metric.',
+ },
+ protocol => {
+ type => 'string',
+ description => 'The protocol where this route was learned from (e.g. BGP).',
+ },
+ 'nexthops' => {
+ type => 'array',
+ description => 'A list of nexthops for the route table entry.',
+ items => {
+ type => 'string',
+ description => 'the interface name or ip address of the next hop',
+ },
+ },
+ },
+ },
+ },
+ code => sub {
+ my ($param) = @_;
+
+ my $zone_id = extract_param($param, 'zone');
+ my $zone = PVE::Network::SDN::Zones::get_zone($zone_id, 1);
+
+ raise_param_exc({
+ zone => "zone does not exist",
+ })
+ if !$zone;
+
+ raise_param_exc({
+ zone => "zone is not an EVPN zone",
+ })
+ if $zone->{type} ne 'evpn';
+
+ my $node_id = extract_param($param, 'node');
+
+ raise_param_exc({
+ zone => "zone does not exist on node $node_id",
+ })
+ if defined($zone->{nodes}) && !grep { $_ eq $node_id } $zone->{nodes}->@*;
+
+ return PVE::RS::SDN::Fabrics::l3vpn_routes($zone_id);
+ },
+});
+
1;
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-11-13 16:19 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 ` Stefan Hanreich [this message]
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 ` [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-11-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.