Good day.
I looking at the internals of bridge layout of openvswitch agent at
http://docs.openstack.org/network-admin/admin/content/figures/2/figures/under-the-hood-scenario-1-ovs-compute.png
and wondering, why this scheme is so complicated and why it use linux
bridge and vethes with
Hi George:
On Wed, Nov 27, 2013 at 1:45 PM, George Shuklin george.shuk...@gmail.comwrote:
Good day.
I looking at the internals of bridge layout of openvswitch agent at
http://docs.openstack.org/network-admin/admin/content/
figures/2/figures/under-the-hood-scenario-1-ovs-compute.png
and
Thank you for reply!
Few more question:
AFAIK bridge tools is not very fast (compare to OVS), so adding them
between OVS and tap (instead of yet another OVS switch) is kinda slow
everything down. Why just not use yet another openvswitch switch to connect
tap to veth devices?
Why iptables, not
On Nov 27, 2013, at 1:29 PM, George Shuklin george.shuk...@gmail.com wrote:
Thank you for reply!
Few more question:
AFAIK bridge tools is not very fast (compare to OVS), so adding them between
OVS and tap (instead of yet another OVS switch) is kinda slow everything
down. Why just not
On Wed, Nov 27, 2013 at 09:29:16PM +0200, George Shuklin wrote:
Why iptables, not internal openvswitch flow rules? Those rules allows to
filter packets on L2-L4 headers and operates very fast. Is some
iptables-only features used in ovs-agent?
I've seen a couple references floating around about
Hi George,
I’m working on a blueprint to implement OVS flows for security groups.
https://blueprints.launchpad.net/neutron/+spec/ovs-firewall-driver Currently,
neutron only implements security groups with iptables even when Open vSwitch is
used.
Amir
On Nov 27, 2013, at 1:29 PM, George
