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

2018-03-22 Thread Armando M.
On 20 March 2018 at 13:48, Ben Pfaff wrote: > On Mon, Mar 19, 2018 at 10:04:00PM -0700, Ben Pfaff wrote: > > 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

Re: [ovs-discuss] (no subject)

2018-03-22 Thread Justin Pettit
> On Mar 22, 2018, at 12:21 AM, Roja Guru wrote: > > hellowhat is the OVS maximum number of flow entries There is no hard limit--only the amount of memory on your system. The rule of thumb we use is roughly 1KB per OpenFlow rule, but that can obviously vary a lot

Re: [ovs-discuss] running userspace openvswitch inside docker

2018-03-22 Thread Nobin Mathew
It is resolved now, https://developers.redhat.com/blog/2016/09/27/logging-in-open-vswitch/ When I run with below commands it works command=/usr/local/sbin/ovsdb-server /etc/openvswitch/conf.db -vconsole:emer -vsyslog:err -vfile:info --remote=punix:/usr/local/var/run/openvswitch/db.sock

[ovs-discuss] running userspace openvswitch inside docker

2018-03-22 Thread Nobin Mathew
Hi, I am trying to bring up openvswitch in docker, to have multiple instance of ovs. I am following these two guides https://github.com/socketplane/docker-ovs/blob/master/README.md http://www.openvswitch.org/support/dist-docs-2.5/INSTALL.userspace.md.html all kernel modules are loaded in host

Re: [ovs-discuss] (no subject)

2018-03-22 Thread Roja Guru
hellowhat is the OVS maximum number of flow entries On Thu, Mar 22, 2018 at 12:47 PM, Roja Guru wrote: > rojarav...@gmail.com > > ___ > discuss mailing list > disc...@openvswitch.org >

[ovs-discuss] (no subject)

2018-03-22 Thread Roja Guru
rojarav...@gmail.com ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] raft ovsdb clustering

2018-03-22 Thread Han Zhou
Sounds good. Just checked the patch, by default the C IDL has "leader_only" as true, which ensures that connection is to leader only. This is the case for northd. So the lock works for northd hot active-standby purpose if all the ovsdb endpoints of a cluster are specified to northd, since all