Comment 1 for bug 1892200

I think that this is pretty good idea for some use cases.
But as keepalived have got tons of different options can You maybe write exactly which of them You want to include and make configurable through neutron config files?

Or maybe we should do it differently and e.g. propose some template of the config file and fill this template with variables, like interface name, IP addresses, etc. for specific router.

That way user may be able to configure whatever keepalived options he would need by preparing this template file to the l3 agent. What do You think about it?