Re: [ovs-discuss] ovs-ofctl memory consumption is large compared to flow bundle size [formatting correction]

[Ben Pfaff]

On Mon, Mar 12, 2018 at 03:47:16PM -0400, Michael Ben-Ami via discuss wrote:
> We found that when we add a flow bundle of about 25MB of textual flows,
> ovs-ofctl ballooned in resident memory to around 563MB. Similarly for a
> bundle about half the size at 12.4MB, ovs-ofctl hit 285MB.

I have a branch in my "reviews" repository that should fix this:
https://github.com/blp/ovs-reviews/tree/memory

It's not quite ready to post for formal review (the commit messages need
work and it probably leaks some memory), but if you have a minute to
test it out, please do consider it.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Turn bridge into a HUB

[Ben Pfaff]

On Mon, Mar 19, 2018 at 07:58:40PM +, Luiz Angelo Daros de Luca wrote:
> Hello,
> 
> I have a physical port receives traffic from mirrored ports in a physical
> (core) switch. I would like to pass these packets to multiple VMs (xen),
> replicating vlan tags when existing.
> 
> With linux bridges, I set aging to 0 and, as it does not understand vlan
> tags, everything works. Now I want to setup the same situation with ovs.
> I'm still a newbie with ovs.
> 
> Xen uses the /etc/xen/scripts/vif-openvswitch that allows me to specify tag
> and trunk argument when a vm port is added (not much besides that). As I
> might receive multiple vlans, I would like to not list all of them.
> 
> I saw that flood_vlans might be useful. I simply need to flood all traffic
> from the physical port on every other port but the physical one,
> replicating vlan tags.

You could set this up with flood_vlans, but you would have to list the
vlans.  ovs-vsctl supports ranges, so you could probably do this easily,
e.g.:
ovs-vsctl set bridge br0 flood_vlans=1-4095

Another way to do this would be to add flows or to use a controller to
add flows.  All you really need is a high-priority flow that does normal
processing for your "regular vlan" and another one that falls back to
flooding, e.g.:

priority=5, vlan_vid=1234, actions=normal
priority=4, actions=flood
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Controller recognizes bridges as hosts!!!

[Ben Pfaff]

It sounds like this is a controller configuration problem.  If you want
the controller to behave differently, then I guess you should configure
it differently.

On Mon, Mar 19, 2018 at 01:21:06PM -0400, Sh j wrote:
> Thank you for your reply.
> 
> The problem is that if I do not assign IP addresses to bridges, these two
> OVSs can not ping each other.
> There are some papers that they use OVSs to connect each other without any
> hosts connected to them (wmSDN).
> In that case, is it possible to configure OVS to avoid the controller to
> recognize IP addresses assigned to bridges as hosts?
> 
> The main problem is that in the mentioned topology the packet_in
> messages to the controller will be different between when we have hosts
> connected to OVSs and when there is no host.
> 
> When the controller considers the IP addresses as host, and node1 running
> OVS1(10.0.0.1) ping node2 running OVS2(10.0.0.2), OVS1 sends ARP request to
> the controller as packet_in. But in case we do not have any host, OVS1 is
> supposed to send  ICMP messages as packet_in to the controller and then
> broadcast ARP to get the MAC address of node2(running OVS2).
> I want to have the second the scenario. Could you help me with
> this configuration?
> 
> Thank you
> 
> 
> 
> 
> On Sun, Mar 18, 2018 at 8:31 PM, Ben Pfaff  wrote:
> 
> > On Sat, Mar 17, 2018 at 08:11:48PM -0400, Sh j wrote:
> > > Hello everyone,
> > >
> > > I configured two OVSs as follows,
> > >
> > > OVS1(eth0) --- (eth0)OVS2
> > >
> > > ovs-vsctl add-br brx
> > > ovs-vsctl add-port brx ethx
> > > ip addr flush dev ethx
> > > ip addr add 10.0.0.x/16 dev brx
> > > ip link set brx up
> > >
> > > Then I set them to connect to a controller as follows,
> > > ovs-vsctl set-controller brx tcp:
> > >
> > >
> > > When I check the discovered topology in the controller, 10.0.0.X
> > addresses
> > > are recognized as hosts connected to OVSs and the MAC address of the OVSs
> > > are considered as MAC address for hosts.
> > >
> > > However, in this case, I do not want to have any hosts, I just want to
> > > configure OVSs to see how they can forward packets between themselves.
> > >
> > > Could you help me with this issue?
> >
> > If you don't want the bridges to have IP addresses, then don't assign
> > them any.
> >
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss