all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-network 05/16] evpn controller: make nodes configurable
Date: Tue, 14 Apr 2026 18:33:02 +0200	[thread overview]
Message-ID: <20260414163315.419384-6-s.hanreich@proxmox.com> (raw)
In-Reply-To: <20260414163315.419384-1-s.hanreich@proxmox.com>

This patch allows restricting an EVPN controller only to specific
nodes in the cluster - similar to the BGP controller. This feature on
its own doesn't add a lot, but is very handy together with other
improvements to the EVPN controller that are implemented in subsequent
patches. Subsequent patches add the ability to define multiple EVPN
controllers, apply route maps to EVPN controllers as well as defining
the type of BGP sessions (all added in separate patches). Together
with this patch, this allows for setting up more complex EVPN setups,
e.g.:

Having an additional EVPN controller on the exit nodes that
communicates with an external EVPN BGP speaker. This allows for
utilizing iBGP internally, but eBGP externally - and only on the exit
nodes. With the addition of route maps, this could be used to
advertise type 2 routes internally, but only type-5 routes externally.

In setups with multiple racks, where the top-of-rack switches act as
route reflectors for the racks, this can be used to define EVPN
peering sessions for each rack independently.

It also allows for the specfic nodes to act as route servers for the
entire cluster that aggregate, modify and re-advertise routes to the
uplink without sitting in the datapath itself. Previously this
required an external route server that handles this outside of the
Promox VE SDN stack. In the future it is planned to implement
configuring EVPN controllers to act as route reflectors, which would
make this setup even better, by adding the ability to scale better for
large clusters.

Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
 src/PVE/API2/Network/SDN/Controllers.pm       | 1 +
 src/PVE/Network/SDN/Controllers/EvpnPlugin.pm | 7 +++++++
 2 files changed, 8 insertions(+)

diff --git a/src/PVE/API2/Network/SDN/Controllers.pm b/src/PVE/API2/Network/SDN/Controllers.pm
index bc3ec09..8633e45 100644
--- a/src/PVE/API2/Network/SDN/Controllers.pm
+++ b/src/PVE/API2/Network/SDN/Controllers.pm
@@ -93,6 +93,7 @@ my $CONTROLLER_PROPERTIES = {
         type => 'string',
         format => 'pve-sdn-isis-net',
     },
+    nodes => get_standard_option('pve-node-list', { optional => 1 }),
 };
 
 __PACKAGE__->register_method({
diff --git a/src/PVE/Network/SDN/Controllers/EvpnPlugin.pm b/src/PVE/Network/SDN/Controllers/EvpnPlugin.pm
index 055a75f..c13d08b 100644
--- a/src/PVE/Network/SDN/Controllers/EvpnPlugin.pm
+++ b/src/PVE/Network/SDN/Controllers/EvpnPlugin.pm
@@ -37,6 +37,7 @@ sub properties {
             type => 'string',
             format => 'ip-list',
         },
+        nodes => get_standard_option('pve-node-list', { optional => 1 }),
     };
 }
 
@@ -47,6 +48,7 @@ sub options {
         'fabric' => { optional => 1 },
         'route-map-in' => { optional => 1 },
         'route-map-out' => { optional => 1 },
+        'nodes' => { optional => 1 },
     };
 }
 
@@ -56,6 +58,11 @@ sub generate_frr_config {
 
     my $local_node = PVE::INotify::nodename();
 
+    if (defined($plugin_config->{nodes})) {
+        my @nodes = PVE::Tools::split_list($plugin_config->{nodes});
+        return if !grep { $_ eq $local_node } @nodes;
+    }
+
     my @peers;
     my $asn = int($plugin_config->{asn});
     my $ebgp = undef;
-- 
2.47.3





  parent reply	other threads:[~2026-04-14 16:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14 16:32 [RFC docs/manager/network/proxmox-ve-rs 00/16] Extend EVPN controller functionality Stefan Hanreich
2026-04-14 16:32 ` [PATCH proxmox-ve-rs 01/16] frr: add local-as setting Stefan Hanreich
2026-04-14 16:32 ` [PATCH proxmox-ve-rs 02/16] frr: add support for extcommunity lists Stefan Hanreich
2026-04-14 16:33 ` [PATCH proxmox-ve-rs 03/16] frr-templates: render local-as setting Stefan Hanreich
2026-04-14 16:33 ` [PATCH proxmox-ve-rs 04/16] frr-templates: render community lists in templates Stefan Hanreich
2026-04-14 16:33 ` Stefan Hanreich [this message]
2026-04-14 16:33 ` [PATCH pve-network 06/16] evpn controller: allow multiple evpn controllers in a cluster Stefan Hanreich
2026-04-14 16:33 ` [PATCH pve-network 07/16] evpn controller: add bgp-mode setting Stefan Hanreich
2026-04-14 16:33 ` [PATCH pve-network 08/16] evpn zone: add secondary-controllers and rt filtering Stefan Hanreich
2026-04-14 16:33 ` [PATCH pve-network 09/16] evpn controller: add ebgp-multihop setting Stefan Hanreich
2026-04-14 16:33 ` [PATCH pve-network 10/16] test: evpn: add test for ibgp + ebgp evpn controller Stefan Hanreich
2026-04-14 16:33 ` [PATCH pve-network 11/16] test: evpn: add legacy test Stefan Hanreich
2026-04-14 16:33 ` [PATCH pve-network 12/16] tests: evpn: force ibgp over ebgp bgp controller with ebgp wan session Stefan Hanreich
2026-04-14 16:33 ` [PATCH pve-network 13/16] tests: test route filtering mechanism with multiple zones/controllers Stefan Hanreich
2026-04-14 16:33 ` [PATCH pve-manager 14/16] sdn: evpn: zone: controller: add new advanced fields Stefan Hanreich
2026-04-14 16:33 ` [PATCH pve-docs 15/16] sdn: evpn: document new zone / controller options Stefan Hanreich
2026-04-14 16:33 ` [PATCH pve-docs 16/16] sdn: fix typo in bgp controller 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=20260414163315.419384-6-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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal