Description of problem: 

OVNK generates the MAC address based on the IP address allocated to the pod. From testing with LACP bond (layer2+3 hash algo), we struggle to have the bond fully utilized. The traffic always picks the same interface. 
To avoid this we could switch to layer3+4 hash algo, but this isn't 802.3ad compliant – while this hash algo uses src port, we can easily saturate the bond. However we would prefer to stay 802.3ad compliant. 

We should make the MAC address creation/assignment random to increase the probability of sharing the link. 

Version-Release number of selected component (if applicable): 4.14z

How reproducible: 100%

Steps to Reproduce:

1. Deploy 4.14+ OCP with LACP bonding (layer2+3)

2. Attempt to saturate the bond (using both interfaces).

Actual results: only 1 interface used.

Expected results: both interfaces used.

Additional info: