Comment 2 for bug 2071323

Great to see the quick feedback.

For now, logging plugin and extenstion for ovs-agent seems not enough for the "Flow log":
1. it does not have each connection statistics data
2. packet is sent to neutron-openvswitch-agent, this is not so much efficiency. OVS-agent is a bit basy with other extensions now. There may be too many packets for ovs-agent to handle normal port_processing.

I'm not very familar with OVS sFlow, but seems it may have it's deficiencies as well:
1. lack of connections match rule for required packets
2. or it mirrors all packets to monitor? Performance side effect for ovs datapath?
3. still needs a new extension to configure the sFlow for ovs-agent