all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Gabriel Goller <g.goller@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH network/proxmox{-ve-rs, -perl-rs} 0/6] Add status endpoints for EVPN statistics
Date: Fri,  5 Sep 2025 13:44:55 +0200	[thread overview]
Message-ID: <20250905114504.195110-1-g.goller@proxmox.com> (raw)

This series adds endpoints to get status information about EVPN FRR
deployments. This is intended to be used mainly in PDM, but could also be
included in the PVE UI in the future.

Put very simply, in EVPN we have two types of Routes: Layer2 routes (with mac
addresses) and Layer3 routes (with ip addresses). In PVE they are separated
nicely when using a Vnet (Layer2) and a Zone (Layer3). This means we can just
add an endpoint for Vnets and Zones and get Layer2 and Layer3 statistics
about the EVPN deployment.

Getting Zone (Layer3) routes is very simple, we just need to find the VRF of
the Zone (which is always named "vrf_{zone}", then get all the routes in the
VRF using frr (`vtysh -c 'show ip route vrf ...'`). Getting VNet (Layer2)
routes is a bit more complicated, we could use `bridge fdb` to get the mac
addresses for the hosts but in order to get more information (like nexthops,
etc.) we again query frr: `vtysh -c 'show bgp l2vpn evpn route vni {vni}'`. The
VNI is the tag of a VNet -- which means we need to read the `.running-config`
beforehand and get all the VNet tags.


This series is based on the fabrics status view series:
https://lore.proxmox.com/pve-devel/20250904114206.193052-1-g.goller@proxmox.com/

proxmox-ve-rs:

Gabriel Goller (3):
  ve-config: add optional tag property to vnet
  frr: fix some route deserialization types
  frr: add deserialization types for EVPN

 proxmox-frr/Cargo.toml                        |   1 +
 proxmox-frr/debian/control                    |   2 +
 proxmox-frr/src/de/evpn.rs                    | 165 ++++++++++++++++++
 proxmox-frr/src/de/mod.rs                     |  13 +-
 proxmox-ve-config/src/sdn/config.rs           |  27 ++-
 proxmox-ve-config/tests/sdn/main.rs           |   5 +-
 .../tests/sdn/resources/running-config.json   |   1 +
 7 files changed, 205 insertions(+), 9 deletions(-)
 create mode 100644 proxmox-frr/src/de/evpn.rs


proxmox-perl-rs:

Gabriel Goller (2):
  pve-rs: sdn: fabrics: update openfabric/ospf route filtering
  pve-rs: sdn: add functions to retrieve the Zone/Vnet routes

 pve-rs/src/bindings/sdn/fabrics.rs |  57 +++++++++++++++
 pve-rs/src/sdn/status.rs           | 114 ++++++++++++++++++++++++++---
 2 files changed, 162 insertions(+), 9 deletions(-)


pve-network:

Gabriel Goller (1):
  sdn: add vnet and zone status endpoints

 src/PVE/API2/Network/SDN/Vnets.pm | 36 +++++++++++++++++++++++++++++++
 src/PVE/API2/Network/SDN/Zones.pm | 26 ++++++++++++++++++++++
 2 files changed, 62 insertions(+)


Summary over all repositories:
  11 files changed, 429 insertions(+), 18 deletions(-)

-- 
Generated by git-murpp 0.8.0


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


             reply	other threads:[~2025-09-05 11:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05 11:44 Gabriel Goller [this message]
2025-09-05 11:44 ` [pve-devel] [PATCH proxmox-ve-rs 1/3] ve-config: add optional tag property to vnet Gabriel Goller
2025-09-05 11:44 ` [pve-devel] [PATCH proxmox-ve-rs 2/3] frr: fix some route deserialization types Gabriel Goller
2025-09-05 11:44 ` [pve-devel] [PATCH proxmox-ve-rs 3/3] frr: add deserialization types for EVPN Gabriel Goller
2025-09-05 11:44 ` [pve-devel] [PATCH proxmox-perl-rs 1/2] pve-rs: sdn: fabrics: update openfabric/ospf route filtering Gabriel Goller
2025-09-05 11:45 ` [pve-devel] [PATCH proxmox-perl-rs 2/2] pve-rs: sdn: add functions to retrieve the Zone/Vnet routes Gabriel Goller
2025-09-05 11:45 ` [pve-devel] [PATCH pve-network 1/1] sdn: add vnet and zone status endpoints Gabriel Goller

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=20250905114504.195110-1-g.goller@proxmox.com \
    --to=g.goller@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal