John,
Thanks your working overtime in last weekend, now we have the following
works to do:
1, submit design spec to networking-sfc
2, submit the RFC to ovs community
3, debug end-to-end about your code changes.
4, submit the initial patch to networking-sfc
5, submit the initial patch to ovs commu
Juno and team,
I have written and compiled (but not tested ) the ovs/ovn interface to
networking-ovn and similarly I have written but not tested the IDL interfaces
on the networking-ovn side. I will put it all together tomorrow and start
debugging end to end. I know I am going to find a lot of
Hi Antonio,
Thanks a lot for your reply.
For ofctl command, it's easy to find how to handle the str and get other
values from ovs cli.
But for controller configuration, like I used postman to configure flow to
OVS,
"Ovs-ofctl dump-flows br0" can get the configured flows,
But do not know how the
hi, everyone
I'm wondering how gre tunnel is implemented in OVS, in the l2gre or the nvgre?
And if it is implemented in l2gre, then what does the tunnel_id field mean for
l2gre, where could i find the standard file?
Thanks,
Chen___
discuss mailing l
Great, glad to hear that it works!
On Sat, Jun 04, 2016 at 12:53:42PM +0200, Elisa Rojas wrote:
> Hi Ben,
>
> After those changes, we realised that we had forgotten to add the --mac
> option again, so our ARP was not valid and that's why the destination was
> not replying. Once solved, the ping f