On 05/08/2025 10:29, 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.
> 
> 
> [1] 
> https://git.proxmox.com/?p=pve-manager.git;a=commit;h=6c5295a1cdb6ec872ddf997cae030817dffff106

Thanks for the patch! Installed on my host that doesn't use fabrics (frr is 
disabled and not running), and when applying the network configuration, frr is 
not enabled.
When applying my SDN configuration (that only uses Simple Zones, no fabrics), 
frr is not enabled either.

I haven't tested on a setup *with* fabrics, though.


_______________________________________________
pve-devel mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Reply via email to