[pve-devel] superseded: [PATCH manager/network v2 0/2] Improve FRR reloading logic

[Stefan Hanreich <s.hanreich@proxmox.com>]

https://lore.proxmox.com/pve-devel/20250805083504.55378-1-s.hanreich@proxmox.com/T/#t

On 8/5/25 10:34 AM, Stefan Hanreich wrote:
> 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.
> 
> Changes from v1:
> * fix typo and improve wording of comments
> 
> 
> [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 | 9 ++++++++-
>  1 file changed, 8 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, 10 insertions(+), 3 deletions(-)
> 



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