As I remember, ovs does not support binding-on veth rules.
Hence now we might need tools like iptables.
However, this might change in future.
As to the l3 part, should be handled in more efficient way, e.g., NFV.
On Tue, Nov 4, 2014 at 2:29 PM, loy wolfe loywo...@gmail.com wrote:
maybe two
At 2014-11-04 14:29:36, loy wolfe loywo...@gmail.com wrote:
maybe two reasons: performance caused by flow miss; feature parity
what do you mean `flow miss`?
L3+ flow table destroy the megaflow aggregation, so if your app has
many concurrent sessions like web server, flow miss upcall
--
Best
Li Tianqing___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
OVS mainly focus on l2 which iptables mainly focus on l3 or higher.
Damon Wang
2014-11-04 11:12 GMT+08:00 Li Tianqing jaze...@163.com:
--
Best
Li Tianqing
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
ovs is implemented open flow, in ovs, it can see the l3, why do not use ovs?
--
Best
Li Tianqing
At 2014-11-04 11:55:46, Damon Wang damon.dev...@gmail.com wrote:
Hi,
OVS mainly focus on l2 which iptables mainly focus on l3 or higher.
Damon Wang
2014-11-04 11:12 GMT+08:00 Li Tianqing
maybe two reasons: performance caused by flow miss; feature parity
L3+ flow table destroy the megaflow aggregation, so if your app has
many concurrent sessions like web server, flow miss upcall would make
vswitchd corrupted.
iptable is already there, migrating it to ovs flow table needs a lot
of
