Hi Yi Yang,
ovs_dpdk worked for me too :)
I was now trying vpp but it does not work. Here are the logs that I get:
http://pastebin.com/ydGEpcJ3
It is a bit strange because I see messages saying that OVS is started and if
for example I access classifier1, I can see OVS there:
vagrant@classifie
Hi Yi Yang,
I found something which might be a bug. In the script run_demo.sh , when
selecting vpp, the following value gets into the demo variable:
demo="./vpp/run_demo_vpp.sh
If I access the script run_demo_vpp.sh, I see the following in line 10:
./common/install_ovs_to_all.sh ${HTTPPROXY} $
Thanks Brady
Patch submitted for review https://git.opendaylight.org/gerrit/#/c/48398
Regards,
Swati
On Tue, Nov 15, 2016 at 7:34 PM, Brady Allen Johnson <
brady.allen.john...@ericsson.com> wrote:
>
> Swati,
>
> It used to be that the SF-type field had to be prefixed with that string.
> Thi
Manuel, good catch, but vpp and ovs has been installed, so it will find it is
ready and exit immediately. For VPP demo, do you restart ODL SFC? vpp renderer
can't coexist with openflow renderer. I suggest you shut down ODL SFC, then
$ rm -rf data snapshots journal instances
$ ./bin/karaf
featur
Hi Yi Yang,
Yes, I restarted the ODL SFC. This is the list of installed features (vpp
features are there):
opendaylight-user@root>feature:list -i
Name| Version | Installed | Repository
| Description
I just merged the patch, thanks!!
A few suggestions:
* I rebased the patch via gerrit.
o You should make sure its rebased off the latest version of
master before submitting it.
o This way you can avoid an unnecessary Jenkins build
* When a change is for a Bugzilla bug, put the
http://meetings.opendaylight.org/opendaylight-sfc/2016/weekly_odl_sfc_meeting__november_16__2016/opendaylight-sfc-weekly_odl_sfc_meeting__november_16__2016.2016-11-16-17.05.html
Brady
___
sfc-dev mailing list
sfc-dev@lists.opendaylight.org
https://lists.
Hi Yi Yang,
I found why it is not working: the SF1 is not returning packets because the
vxlan_tool is dropping them. The reason is that SFF1 is not adding the right
destination IP to the packets. The IP of SFF1 is 192.168.70.20 and the IP of
the SF1 is 192.168.70.30. The packets that arrive to
Hi Brady,
When we come back to SFC version 0.4.0-SNAPSHOT, it works fine, this error
just appear when using the version 0.5.0-SNAPSHOT.
BTW, we don't have any code into the NIC using the class
"org.opendaylight.sfc.provider.OpendaylightSfc". I'll revert the commit
that changes the SFC to 0.5.0-SN
Can you see interfaces " vxlan_gpe_tunnel1" and " vxlan_gpe_tunnel2" in sff1
and sff2 by the cmd "sudo vppctl show int"?
-Original Message-
From: Manuel Buil [mailto:manuel.b...@ericsson.com]
Sent: Wednesday, November 16, 2016 9:35 PM
To: Yang, Yi Y ; 'sfc-dev@lists.opendaylight.org'
10 matches
Mail list logo
