[pdm-devel] [PATCH network/proxmox{, -backup, -api-types, -datacenter-manager} v4 00/30] Add initial SDN / EVPN integration

[Hannes Duerr]

better late than never, some things I noticed while testing this
series.

I tested the series with two evpn Clusters which we're not peering
each other but just coexisted.
I added them as remotes and got the overview of the existing zones and
vnets. Afterwards i removed the existing Zones in one Cluster and
added another zone and vnet via PDM.

Adding new zones works very smoothly, but it doesn't seem to be very
useful yet, as important configuration options such as route target
import and exit nodes are still missing, and you still have to
configure these options directly in the Proxmox VE cluster.
-> This is not listed as future work, but I think stefan told me
of-list that this is of course also planned to be added.
Adding vnets also works very smoothly.

The UI is also very pleasant, and you get a good overview of your
EVPN deployments, which I really like.

I will continue testing next week and I am planning on adding another
cluster to peer against an existing Cluster.
I also didn't yet manage to test the rollback mechanisms and some edge
case testing.


On Thu Sep 4, 2025 at 10:18 AM CEST, Stefan Hanreich wrote:
[...]
> ## Future Work
> * show the output of the new status API calls created by Gabriel in the views.
> * add a functionality for grouping remotes together, instead of implicitly
>   grouping them based on ASN:VNI
What about showing more information about the EVPN Controller as well?
I think it would be nice to have the peering information of the EVPN
controller shown in the UI as well, this would also make the
grouping/assignment easier.
For example, in a spine/leaf architecture where a PVE cluster is
located in a rack with ToR switches as leaves and the EVPN controller
in the cluster peers with the spine switch which could be a Route
Reflector. Here, you would see that several EVPN zones peer with the
same spine switch and therefore belong together.