Hi,
is there any documentation on Python binding (
https://github.com/openvswitch/ovs/tree/master/python )?
Is there any documentation on the underlying TCP/JSON protocol?
Thanks,
Sergiy.
___
discuss mailing list
disc...@openvswitch.org
I investigated this a little bit by putting the following in a file
named 'flows':
table=0 ip,in_port=4,dl_dst=a6:c1:a7:15:a4:3d,nw_dst=10.39.176.4,priority=3100,
actions=resubmit(,25)
table=25, ip,vlan_tci=0x1000/0x1000,nw_dst=10.39.176.4, priority=3100,
On Tue, May 07, 2019 at 02:30:25PM -0700, Thiago Santos wrote:
> On Tue, May 7, 2019 at 1:58 PM Ben Pfaff wrote:
>
> > On Tue, May 07, 2019 at 12:05:43PM -0700, Thiago Santos wrote:
> > > Hello,
> > >
> > > I've been using OVS Conntrack integration for Source NAT and setting the
> > >
Greetings,
I have been using ofproto/trace to verify the actions taken on various
packets through an OVS bridge. My methodology is basically to specify
the action in br_flow format to ovs-appctl ofproto/trace and then
comparing the datapath actions line with expected actions. I ran into
an
On Tue, May 7, 2019 at 1:58 PM Ben Pfaff wrote:
> On Tue, May 07, 2019 at 12:05:43PM -0700, Thiago Santos wrote:
> > Hello,
> >
> > I've been using OVS Conntrack integration for Source NAT and setting the
> > Destination IP directly but this is having the side effect of overwriting
> > the
On Tue, May 7, 2019 at 9:56 AM Justin Pettit wrote:
>
> Hi, Daniel. I don't think this is a bad approach. However, at the
moment, Han's work is with ovn-controller and ddlog is with ovn-northd.
We've talked about using ddlog in ovn-controller, but there's been no work
in that direction yet. At
On Tue, May 07, 2019 at 12:05:43PM -0700, Thiago Santos wrote:
> Hello,
>
> I've been using OVS Conntrack integration for Source NAT and setting the
> Destination IP directly but this is having the side effect of overwriting
> the Conntrack set SNAT IP. I simplified my rules to look like this to
Hello,
I've been using OVS Conntrack integration for Source NAT and setting the
Destination IP directly but this is having the side effect of overwriting
the Conntrack set SNAT IP. I simplified my rules to look like this to
reproduce the problem:
cookie=0x0, duration=90070.633s, table=0,
Hi, Daniel. I don't think this is a bad approach. However, at the moment,
Han's work is with ovn-controller and ddlog is with ovn-northd. We've talked
about using ddlog in ovn-controller, but there's been no work in that direction
yet. At this point, I think Han's patches should be
On Mon, May 6, 2019 at 6:04 PM Aaron Conole wrote:
> Jaime Caamaño Ruiz writes:
>
> >> Agree. I will try to address this issue. I think we can have a
> >> separate
> >> run time/log directory for OVN. ovn-controller needs to talk to the
> >> local ovsdb-server
> >> and br-int.mgmt and other
Hi folks,
After some conversations with Han (thanks for your time and great
talk!) at the Open Infrastructure Summit in Denver last week, here I
go with this - somehow crazy - idea.
Since DDlog approach for incremental processing is not going to happen
soon and Han's reported his patches to be
When the datapath in kernel sends upcall request to vswitchd in the userspace,
which upcall_handler thread in vswitch will deal with this upcall request?
What's the criteria for dispatching a certain upcall to a certain
upcall_handler?
Much thanks
Following up on this since it is still an issue.
strace on the thread in question shows the following:
13:35:47 poll([{fd=23, events=POLLIN}], 1, 0) = 0 (Timeout) <0.18>
13:35:47 epoll_wait(42, [{EPOLLIN, {u32=3, u64=3}}], 9, 0) = 1 <0.18>
13:35:47 recvmsg(417, {msg_namelen=0},
So is there any way to have TSO work with OVS-DPDK? Are there any patches
which can be applied? Because I followed this Intel page and the author was
able to get the 2.5x higher throughput for OVS-DPDK as compared to native
OVS.
14 matches
Mail list logo
