Bug 1432398

1. Proposed title of this feature request  
keepalived with VRRP version 3 support
--------------------------------------------------------------------------      
2. What is the nature and description of the request?  
keepalived is a routing software which mail goal is to provide simple and robust facilities for loadbalancing and high-availability to Linux Systems. This high-availability is archived by the VRRP protocol. Since 2015-05-31 and release 1.2.17 keepalived supports VRRP version 3 in addition to version 2. In VRRP version 2 the smallest available interval to check if the other nodes are still available is one second, while in VRRP version 3 it is 1 centisecond. With modern Hardware and 10GB/s infrastructure the load and traffic created by this checks are no longer important.
--------------------------------------------------------------------------
3. Why do you customer need this? (List the business requirements here)  
It is needed for multiple high-available router clusters, that we plan to setup for our data center infrastructure
--------------------------------------------------------------------------
4. How would you like to achieve this? (List the functional requirements here)  
either a backport of the functionality or minor patch
--------------------------------------------------------------------------
5. For each functional requirement listed, specify how Red Hat and you can test to confirm the requirement is successfully implemented.  
Example configuration once the feature is backported/minor update happened:
- Install keepalived on two systems. 
- Download attached file and replace all values marked with the <> [including the <>]
- Replace file /etc/keepalived/keepalived.conf with this changed keepalived.conf on both Systems
- (re)start the keepalived service with "/bin/systemctl restart  keepalived.service" on both Systems
- check with "ip a" if only one system has the ip address configured in the keepalived.conf. !!If both have the ip the communication between the two systems is not possible and it will fail either way!!
- start and keep pinging the ip address configured in the keepalived.conf with a third System
- restart the keepalived service again on the system with the configured IP.
- if the ping did not lose any packets it has worked! if it did lose packets and it did take about 3 seconds for the ping to continue, it didnt work.
--------------------------------------------------------------------------
6. Do you have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
RHEL 7 - ASAP ;-)
--------------------------------------------------------------------------
7. Is the sales team involved in this request and do they have any additional input?  
No, please let us know if this is required.
--------------------------------------------------------------------------
8. List any affected components.  
keepalived
--------------------------------------------------------------------------
9. Would you be able to assist in testing this functionality if implemented?  
yes.