Obsolete due to:
https://lore.proxmox.com/pve-devel/20250522161731.537011-1-s.hanre...@proxmox.com/
___
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
On 12.02.2025 12:17, Stefan Hanreich wrote:
This still has some issues (see below), maybe we can look at it together
next week (will be gone after today) and see if we can make some
additional structural improvements to the whole controller / frr logic?
There were also some regressions/bugs wi
This still has some issues (see below), maybe we can look at it together
next week (will be gone after today) and see if we can make some
additional structural improvements to the whole controller / frr logic?
There were also some regressions/bugs with FRR config generation while
testing, so this
On 2/11/25 21:30, Thomas Lamprecht wrote:
> Looks OK otherwise, albeit I mostly skimmed it a few days ago and had
> this lying around as draft, somebody else (@Stefan) checking would not
> hurt.
wanted to look into it, will do so today
___
pve-devel ma
Am 05.02.25 um 17:13 schrieb Gabriel Goller:
> Previously the frr config generation and writing was only done in the
> evpn plugin. This means that it was not possible to create a standalone
> bgp and isis plugin without an evpn plugin in place. (The config would
> just never be written.) To fix th
Previously the frr config generation and writing was only done in the
evpn plugin. This means that it was not possible to create a standalone
bgp and isis plugin without an evpn plugin in place. (The config would
just never be written.) To fix this, factor out the frr generation and
writing into a
