Some additional research
Without "hash" method, ovs will use the default xlate_default_select_group() method, which uses all these parameters: https://github.com/openvswitch/ovs/commit/1d1aae0b2f9a149bf74000d975fbf29d133cd9ca
So load balancing should actually be OK, even if not on the fields specified in the spec: https://github.com/openstack/networking-sfc/blob/master/doc/source/ovs_driver_and_agent_workflow.rst#group-table-flows
The fix should be: * enable OpenFlow 1.5 * set selection_method to "hash" * use lb_fields for selection parameters * else use default selection parameters ip_src,nw_proto,tp_src
Does this sound right?
Some additional research
Without "hash" method, ovs will use the default xlate_default_ select_ group() method, which uses all these parameters: /github. com/openvswitch /ovs/commit/ 1d1aae0b2f9a149 bf74000d975fbf2 9d133cd9ca
https:/
So load balancing should actually be OK, even if not on the fields specified in the spec: /github. com/openstack/ networking- sfc/blob/ master/ doc/source/ ovs_driver_ and_agent_ workflow. rst#group- table-flows
https:/
The fix should be: nw_proto, tp_src
* enable OpenFlow 1.5
* set selection_method to "hash"
* use lb_fields for selection parameters
* else use default selection parameters ip_src,
Does this sound right?