From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 1A89A1FF15C for ; Fri, 5 Sep 2025 14:37:41 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9627714896; Fri, 5 Sep 2025 14:37:57 +0200 (CEST) Mime-Version: 1.0 Date: Fri, 05 Sep 2025 14:37:24 +0200 Message-Id: Cc: "pdm-devel" From: "Hannes Duerr" To: "Proxmox Datacenter Manager development discussion" X-Mailer: aerc 0.20.1-0-g2ecb8770224a-dirty References: <20250904081900.12655-1-s.hanreich@proxmox.com> In-Reply-To: <20250904081900.12655-1-s.hanreich@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1757075826855 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.073 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pdm-devel] [PATCH network/proxmox{, -backup, -api-types, -datacenter-manager} v4 00/30] Add initial SDN / EVPN integration X-BeenThere: pdm-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Datacenter Manager development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Datacenter Manager development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pdm-devel-bounces@lists.proxmox.com Sender: "pdm-devel" 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. _______________________________________________ pdm-devel mailing list pdm-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel