[pve-devel] [PATCH manager/network v2 0/2] Improve FRR reloading logic
Hannes Duerr
h.duerr at proxmox.com
Tue Aug 5 11:43:15 CEST 2025
Tested it by upgrading existing ceph full mesh cluster (without
fabrics) and reloading the network after succesful upgrade
Tested-by: Hannes Duerr <h.duerr at proxmox.com>
On Tue Aug 5, 2025 at 10:35 AM CEST, 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
>
More information about the pve-devel
mailing list