From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 4B08C1FF16F for ; Tue, 5 Aug 2025 10:28:32 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 224DA921A; Tue, 5 Aug 2025 10:29:59 +0200 (CEST) From: Stefan Hanreich To: pve-devel@lists.proxmox.com Date: Tue, 5 Aug 2025 10:29:22 +0200 Message-ID: <20250805082926.48280-1-s.hanreich@proxmox.com> X-Mailer: git-send-email 2.47.2 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.191 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 KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Subject: [pve-devel] [PATCH manager/network 0/2] Improve FRR reloading logic X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Follow-up to the stop gap fix in [1]. This should handle all cases that we need to consider: * Do not overwrite existing FRR configurations, unless we need to generate our own FRR configuration. * Do not trigger a FRR enable when reloading the host configuration, even though there is no FRR configuration. * Overwrite the FRR configuration with an empty configuration if all SDN entities using FRR got deleted. * Regenerate the FRR configuration when the host network configuration changes, since this might affect the generated FRR configuration. [1] https://git.proxmox.com/?p=pve-manager.git;a=commit;h=6c5295a1cdb6ec872ddf997cae030817dffff106 pve-manager: Stefan Hanreich (1): network: improve reloading logic PVE/API2/Network.pm | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) pve-network: Stefan Hanreich (1): sdn: api: always send regenerate-frr parameter src/PVE/API2/Network/SDN.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) Summary over all repositories: 2 files changed, 9 insertions(+), 3 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