Page MenuHomeVyOS Platform

Remove keepalived in favor of FRR for VRRP
Open, Requires assessmentPublicFEATURE REQUEST

Description

Hi,

looking at FRR ( http://docs.frrouting.org/en/latest/vrrp.html ) it would seem to be nice to throw out keepalived and replace it with FRR ...

Regards,

Primoz

Details

Difficulty level
Unknown (require assessment)
Version
-
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Improvement (missing useful functionality)

Event Timeline

erkin renamed this task from VRRP @ FRR to Remove keepalived in favor of FRR for VRRP.Aug 30 2021, 6:16 AM
erkin set Issue type to Improvement (missing useful functionality).
erkin removed a subscriber: Active contributors.

If the FRR/vrrpd is good enough then the main benefit is that the FRR/vrrpd is already included so no need to also include and use keepalived (unnecessary files and binaries and dependencies).

Things to verify however before a switch is performed (and keepalived is thrown out) is support for vrf/namespaces, various interface and other tracking and multicast vs unicast (it seems that keepalived supports them all - dunno about FRR/vrrpd).

https://docs.frrouting.org/en/latest/vrrp.html

If the FRR/vrrpd is good enough then the main benefit is that the FRR/vrrpd is already included so no need to also include and use keepalived (unnecessary files and binaries and dependencies).

Things to verify however before a switch is performed (and keepalived is thrown out) is support for vrf/namespaces, various interface and other tracking and multicast vs unicast (it seems that keepalived supports them all - dunno about FRR/vrrpd).

https://docs.frrouting.org/en/latest/vrrp.html

@Apachez We can't delete the keeaplived package, as we use set high-availability virtual-server xxx which is part of keepalived.

Well in that case it boils down to if the FRR/vrrpd supports namespaces, various tracking (interface etc) aswell as multicast vs unicast which keepalived seems to support them all.

If keepalived will be kept for vrrp perhaps FRR/vrrpd could be deleted from the compile (unless the set high-availability vrrp will be expanded with a "flavour" setting to choose between keepalived and FRR/vrrpd)?