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

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

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