Page MenuHomeVyOS Platform
Create Task
Maniphest T2444

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

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

primoz created this task.May 10 2020, 7:53 AM
pasik added a subscriber: pasik.May 10 2020, 3:56 PM
Viacheslav added a subscriber: Viacheslav.Dec 22 2020, 4:50 PM

@primoz What are the benefits?

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.
syncer edited projects, added VyOS 1.3 Equuleus (1.3.0); removed VyOS 1.3 Equuleus.Nov 6 2021, 11:24 AM
syncer edited projects, added VyOS 1.3 Equuleus (1.3.3); removed VyOS 1.3 Equuleus (1.3.0).Aug 29 2022, 7:05 AM
syncer edited projects, added VyOS 1.3 Equuleus (1.3.4); removed VyOS 1.3 Equuleus (1.3.3).Jul 12 2023, 9:42 PM
syncer edited projects, added VyOS 1.3 Equuleus (1.3.5); removed VyOS 1.3 Equuleus (1.3.4).Aug 25 2023, 9:30 PM
Viacheslav edited projects, added VyOS 1.4 Sagitta; removed VyOS 1.3 Equuleus (1.3.5).Aug 28 2023, 1:23 PM
Viacheslav edited projects, added VyOS 1.5 Circinus; removed VyOS 1.4 Sagitta.Tue, Sep 5, 12:04 PM
Apachez added a subscriber: Apachez.Tue, Sep 5, 4:58 PM

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

Viacheslav added a comment.Tue, Sep 5, 5:54 PM
In T2444#158779, @Apachez wrote:

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.

Apachez added a comment.Tue, Sep 5, 6:10 PM

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)?