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
-----------------------------------------------------------------------------------------------------------------------------------------------------------
odl-config-netty | 0.6.0-SNAPSHOT | x |
odl-config-persister-0.6.0-SNAPSHOT | OpenDaylight :: Config-Netty
odl-netconf-connector-all | 1.2.0-SNAPSHOT | x |
odl-controller-1.2.0-SNAPSHOT | OpenDaylight :: Netconf Connector :: All
odl-netconf-connector | 1.2.0-SNAPSHOT | x |
odl-controller-1.2.0-SNAPSHOT | OpenDaylight :: Netconf Connector ::
Netconf Conne
odl-netconf-connector-ssh | 1.2.0-SNAPSHOT | x |
odl-controller-1.2.0-SNAPSHOT | OpenDaylight :: Netconf Connector ::
Netconf Conne
odl-netconf-topology | 1.2.0-SNAPSHOT | x |
odl-controller-1.2.0-SNAPSHOT | OpenDaylight :: Netconf Topology ::
Netconf Connec
odl-sfc-model | 0.5.0-SNAPSHOT | x |
odl-sfc-0.5.0-SNAPSHOT | OpenDaylight :: sfc :: Model
odl-sfc-provider | 0.5.0-SNAPSHOT | x |
odl-sfc-0.5.0-SNAPSHOT | OpenDaylight :: sfc :: Provider
odl-sfc-provider-rest | 0.5.0-SNAPSHOT | x |
odl-sfc-0.5.0-SNAPSHOT | OpenDaylight :: sfc :: Provider
odl-sfc-vpp-renderer | 0.5.0-SNAPSHOT | x |
odl-sfc-0.5.0-SNAPSHOT | OpenDaylight :: sfc-renderers :: VPP
Renderer
odl-sfc-ui | 0.5.0-SNAPSHOT | x |
odl-sfc-0.5.0-SNAPSHOT | OpenDaylight :: sfc :: UI
odl-yangtools-yang-data | 1.1.0-SNAPSHOT | x |
odl-yangtools-1.1.0-SNAPSHOT | OpenDaylight :: Yangtools :: Data
Binding
odl-yangtools-common | 1.1.0-SNAPSHOT | x |
odl-yangtools-1.1.0-SNAPSHOT | OpenDaylight :: Yangtools :: Common
odl-yangtools-yang-parser | 1.1.0-SNAPSHOT | x |
odl-yangtools-1.1.0-SNAPSHOT | OpenDaylight :: Yangtools :: YANG Parser
odl-netty | 4.0.37.Final | x |
odlparent-1.8.0-SNAPSHOT | OpenDaylight :: Netty
odl-lmax | 3.3.4 | x |
odlparent-1.8.0-SNAPSHOT | OpenDaylight :: LMAX Disruptor
odl-netconf-api | 1.2.0-SNAPSHOT | x |
odl-netconf-1.2.0-SNAPSHOT | OpenDaylight :: Netconf :: API
odl-netconf-mapping-api | 1.2.0-SNAPSHOT | x |
odl-netconf-1.2.0-SNAPSHOT | OpenDaylight :: Netconf :: Mapping API
odl-netconf-util | 1.2.0-SNAPSHOT | x |
odl-netconf-1.2.0-SNAPSHOT |
odl-netconf-impl | 1.2.0-SNAPSHOT | x |
odl-netconf-1.2.0-SNAPSHOT | OpenDaylight :: Netconf :: Impl
odl-config-netconf-connector | 1.2.0-SNAPSHOT | x |
odl-netconf-1.2.0-SNAPSHOT | OpenDaylight :: Netconf :: Connector
odl-netconf-netty-util | 1.2.0-SNAPSHOT | x |
odl-netconf-1.2.0-SNAPSHOT | OpenDaylight :: Netconf :: Netty Util
odl-netconf-client | 1.2.0-SNAPSHOT | x |
odl-netconf-1.2.0-SNAPSHOT | OpenDaylight :: Netconf :: Client
odl-netconf-monitoring | 1.2.0-SNAPSHOT | x |
odl-netconf-1.2.0-SNAPSHOT | OpenDaylight :: Netconf :: Monitoring
odl-netconf-notifications-api | 1.2.0-SNAPSHOT | x |
odl-netconf-1.2.0-SNAPSHOT | OpenDaylight :: Netconf :: Notification
:: Api
odl-netconf-notifications-impl | 1.2.0-SNAPSHOT | x |
odl-netconf-1.2.0-SNAPSHOT | OpenDaylight :: Netconf :: Monitoring
:: Impl
odl-netconf-ssh | 1.2.0-SNAPSHOT | x |
odl-netconf-1.2.0-SNAPSHOT | OpenDaylight :: Netconf Connector :: SSH
odl-netconf-tcp | 1.2.0-SNAPSHOT | x |
odl-netconf-1.2.0-SNAPSHOT | OpenDaylight :: Netconf Connector :: TCP
odl-aaa-netconf-plugin | 1.2.0-SNAPSHOT | x |
odl-netconf-1.2.0-SNAPSHOT | OpenDaylight :: AAA :: ODL NETCONF
Plugin
odl-aaa-api | 0.5.0-SNAPSHOT | x |
odl-aaa-0.5.0-SNAPSHOT | OpenDaylight :: AAA :: APIs
odl-aaa-authn | 0.5.0-SNAPSHOT | x |
odl-aaa-0.5.0-SNAPSHOT | OpenDaylight :: AAA :: Authentication -
NO CLUSTER
odl-akka-scala | 2.11 | x |
odl-controller-1.8.0-SNAPSHOT | Scala Runtime for OpenDaylight
odl-akka-system | 2.4.11 | x |
odl-controller-1.8.0-SNAPSHOT | Akka Actor Framework System Bundles
odl-akka-clustering | 2.4.11 | x |
odl-controller-1.8.0-SNAPSHOT | Akka Clustering
odl-akka-leveldb | 0.7 | x |
odl-controller-1.8.0-SNAPSHOT | LevelDB
odl-akka-persistence | 2.4.11 | x |
odl-controller-1.8.0-SNAPSHOT | Akka Persistence
odl-config-all | 0.6.0-SNAPSHOT | x |
odl-config-0.6.0-SNAPSHOT | OpenDaylight :: Config :: All
odl-config-api | 0.6.0-SNAPSHOT | x |
odl-config-0.6.0-SNAPSHOT | OpenDaylight :: Config :: API
odl-config-netty-config-api | 0.6.0-SNAPSHOT | x |
odl-config-0.6.0-SNAPSHOT | OpenDaylight :: Config :: Netty Config
API
odl-config-core | 0.6.0-SNAPSHOT | x |
odl-config-0.6.0-SNAPSHOT | OpenDaylight :: Config :: Core
odl-config-manager | 0.6.0-SNAPSHOT | x |
odl-config-0.6.0-SNAPSHOT | OpenDaylight :: Config :: Manager
odl-ovsdb-southbound-api | 1.4.0-SNAPSHOT | x |
odl-ovsdb-southbound-1.4.0-SNAPSHOT | OpenDaylight :: southbound :: api
odl-mdsal-models | 0.10.0-SNAPSHOT | x |
odl-mdsal-models-0.10.0-SNAPSHOT | OpenDaylight :: MD-SAL :: Models
standard | 3.0.8 | x | standard-3.0.8
| Karaf standard feature
config | 3.0.8 | x | standard-3.0.8
| Provide OSGi ConfigAdmin support
region | 3.0.8 | x | standard-3.0.8
| Provide Region Support
package | 3.0.8 | x | standard-3.0.8
| Package commands and mbeans
http | 3.0.8 | x | standard-3.0.8
| Implementation of the OSGI HTTP Service
war | 3.0.8 | x | standard-3.0.8
| Turn Karaf as a full WebContainer
kar | 3.0.8 | x | standard-3.0.8
| Provide KAR (KARaf archive) support
ssh | 3.0.8 | x | standard-3.0.8
| Provide a SSHd server on Karaf
management | 3.0.8 | x | standard-3.0.8
| Provide a JMX MBeanServer and a set of MBeans in K
odl-mdsal-dom | 2.2.0-SNAPSHOT | x |
odl-yangtools-2.2.0-SNAPSHOT | OpenDaylight :: MD-SAL :: DOM
odl-mdsal-common | 2.2.0-SNAPSHOT | x |
odl-yangtools-2.2.0-SNAPSHOT | OpenDaylight :: MD-SAL :: DOM Broker
odl-mdsal-dom-api | 2.2.0-SNAPSHOT | x |
odl-yangtools-2.2.0-SNAPSHOT | OpenDaylight :: MD-SAL :: DOM API & SPI
odl-mdsal-dom-broker | 2.2.0-SNAPSHOT | x |
odl-yangtools-2.2.0-SNAPSHOT | OpenDaylight :: MD-SAL :: DOM Broker
odl-mdsal-binding-base | 2.2.0-SNAPSHOT | x |
odl-yangtools-2.2.0-SNAPSHOT | OpenDaylight :: MD-SAL :: Binding Base
Concepts
odl-mdsal-binding-runtime | 2.2.0-SNAPSHOT | x |
odl-yangtools-2.2.0-SNAPSHOT | OpenDaylight :: MD-SAL :: Binding
Generator
odl-mdsal-binding-api | 2.2.0-SNAPSHOT | x |
odl-yangtools-2.2.0-SNAPSHOT | OpenDaylight :: MD-SAL :: Binding Base
Concepts
odl-mdsal-binding-dom-adapter | 2.2.0-SNAPSHOT | x |
odl-yangtools-2.2.0-SNAPSHOT | OpenDaylight :: MD-SAL :: Binding
Generator
odl-mdsal-eos-common | 2.2.0-SNAPSHOT | x |
odl-yangtools-2.2.0-SNAPSHOT | OpenDaylight :: MD-SAL :: EOS :: Common
odl-mdsal-eos-dom | 2.2.0-SNAPSHOT | x |
odl-yangtools-2.2.0-SNAPSHOT | OpenDaylight :: MD-SAL :: EOS :: DOM
odl-mdsal-eos-binding | 2.2.0-SNAPSHOT | x |
odl-yangtools-2.2.0-SNAPSHOT | OpenDaylight :: MD-SAL :: EOS :: Binding
odl-mdsal-singleton-common | 2.2.0-SNAPSHOT | x |
odl-yangtools-2.2.0-SNAPSHOT | OpenDaylight :: MD-SAL :: Singleton ::
Common
odl-mdsal-singleton-dom | 2.2.0-SNAPSHOT | x |
odl-yangtools-2.2.0-SNAPSHOT | OpenDaylight :: MD-SAL :: Singleton ::
DOM
odl-aaa-shiro | 0.5.0-SNAPSHOT | x |
odl-aaa-0.5.0-SNAPSHOT | OpenDaylight :: AAA :: Shiro
odl-config-persister | 0.6.0-SNAPSHOT | x |
odl-config-persister-0.6.0-SNAPSHOT | OpenDaylight :: Config Persister
odl-config-startup | 0.6.0-SNAPSHOT | x |
odl-config-persister-0.6.0-SNAPSHOT | OpenDaylight :: Config Persister::
Config Startup
odl-config-manager-facade-xml | 0.6.0-SNAPSHOT | x |
odl-config-persister-0.6.0-SNAPSHOT | Opendaylight :: Config Persister::
Mapping for Con
pax-jetty | 8.1.19.v20160209 | x |
org.ops4j.pax.web-3.2.9 | Provide Jetty engine support
pax-http | 3.2.9 | x |
org.ops4j.pax.web-3.2.9 | Implementation of the OSGI HTTP Service
pax-http-whiteboard | 3.2.9 | x |
org.ops4j.pax.web-3.2.9 | Provide HTTP Whiteboard pattern support
pax-war | 3.2.9 | x |
org.ops4j.pax.web-3.2.9 | Provide support of a full WebContainer
odl-mdsal-common | 1.5.0-SNAPSHOT | x |
odl-mdsal-1.5.0-SNAPSHOT | OpenDaylight :: Config :: All
odl-mdsal-broker-local | 1.5.0-SNAPSHOT | x |
odl-mdsal-1.5.0-SNAPSHOT | OpenDaylight :: MDSAL :: Broker
odl-mdsal-clustering-commons | 1.5.0-SNAPSHOT | x |
odl-mdsal-1.5.0-SNAPSHOT |
odl-mdsal-distributed-datastore | 1.5.0-SNAPSHOT | x |
odl-mdsal-1.5.0-SNAPSHOT |
odl-mdsal-remoterpc-connector | 1.5.0-SNAPSHOT | x |
odl-mdsal-1.5.0-SNAPSHOT |
odl-mdsal-broker | 1.5.0-SNAPSHOT | x |
odl-mdsal-1.5.0-SNAPSHOT |
odl-dlux-core | 0.5.0-SNAPSHOT | x |
odl-dlux-0.5.0-SNAPSHOT | Opendaylight dlux minimal feature
odl-restconf | 1.5.0-SNAPSHOT | x |
odl-controller-1.5.0-SNAPSHOT | OpenDaylight :: Restconf
odl-restconf-noauth | 1.5.0-SNAPSHOT | x |
odl-controller-1.5.0-SNAPSHOT | OpenDaylight :: Restconf
odl-mdsal-apidocs | 1.5.0-SNAPSHOT | x |
odl-controller-1.5.0-SNAPSHOT | OpenDaylight :: MDSAL :: APIDOCS
odl-protocol-framework | 0.9.0-SNAPSHOT | x |
odl-protocol-framework-0.9.0-SNAPSHOT | OpenDaylight :: Protocol Framework
I checked the command you told me and sff1 has statistics:
vxlan_gpe_tunnel0 2 up rx packets
8
rx bytes
976
But sff2 does not have statistics in the vxlan_gpe interface:
vxlan_gpe_tunnel0 2 up
Any idea what might be the problem?
One extra question: if I understood it well, VPP then is only deployed in sff1
and sff2. Classifiers are still using OVS, right? Is there any reason for this?
Regards,
Manuel
-----Original Message-----
From: Yang, Yi Y [mailto:[email protected]]
Sent: Wednesday, November 16, 2016 2:00 PM
To: Manuel Buil <[email protected]>; '[email protected]'
<[email protected]>
Subject: RE: Welcome you to try sfc104 demo
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
feature:install odl-sfc-vpp-renderer odl-sfc-ui
This will make sure a clean ODL SFC.
You can also check if sff1 and sff2 have packets processed by the below cmds
$ sudo vppctl show int
vxlan-gpe interfaces should have rx and tx statistics.
-----Original Message-----
From: Manuel Buil [mailto:[email protected]]
Sent: Wednesday, November 16, 2016 7:06 PM
To: Yang, Yi Y <[email protected]>; '[email protected]'
<[email protected]>
Subject: RE: Welcome you to try sfc104 demo
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} ${HTTPSPROXY}
But probably it should be:
./common/install_vpp_to_all.sh ${HTTPPROXY} ${HTTPSPROXY}
Note that ./common/install_vpp_to_all.sh exists. I will change that line and
see what happens.
Regards,
Manuel
-----Original Message-----
From: Manuel Buil
Sent: Wednesday, November 16, 2016 9:28 AM
To: Yang, Yi Y <[email protected]>; [email protected]
Subject: RE: Welcome you to try sfc104 demo
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@classifier1:~$ sudo ovs-vsctl show
3dc8d465-571f-4bf7-8125-ecb7d06bccd4
Bridge br-sfc
Port "dpdk0"
Interface "dpdk0"
type: dpdk
Port br-sfc
Interface br-sfc
type: internal
Port "vxlangpe0"
Interface "vxlangpe0"
type: vxlan
options: {dst_port="4790", exts=gpe, key=flow, remote_ip=flow}
Port veth-br
Interface veth-br
ovs_version: "2.5.90"
Am I perhaps doing anything wrong? I thought that OVS should not be out of the
picture as VPP is taking the dataplane role.
By the way, can you tell me any useful vpp command to check things?
Thanks,
Manuel
-----Original Message-----
From: Yang, Yi Y [mailto:[email protected]]
Sent: Tuesday, November 15, 2016 10:35 AM
To: Manuel Buil <[email protected]>; [email protected]
Subject: RE: Welcome you to try sfc104 demo
Manuel, very good, I'm very happy to see this result :-), for OVS DPDK and VPP,
the same environment is ok, just you need to make sure SFC is really ready for
the demo, run_demo.sh just does some simple check.
-----Original Message-----
From: Manuel Buil [mailto:[email protected]]
Sent: Tuesday, November 15, 2016 5:16 PM
To: Yang, Yi Y <[email protected]>; [email protected]
Subject: RE: Welcome you to try sfc104 demo
Hi Yi Yang,
Using the latest build of Carbon branch works :).
I will now try ovs-dpdk. Any requirements here? For example, I guess I need to
run it in a server with NICs that support DPDK, right? Do you know a way to
check if they do?
Regards,
Manuel
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Manuel Buil
Sent: Tuesday, November 15, 2016 9:06 AM
To: Yang, Yi Y <[email protected]>; [email protected]
Subject: Re: [sfc-dev] Welcome you to try sfc104 demo
Hi,
I am using ODL Boron SR1, the release that came out 3 weeks ago.
I'll switch to master and check.
Regards,
Manuel
-----Original Message-----
From: Yang, Yi Y [mailto:[email protected]]
Sent: Tuesday, November 15, 2016 1:42 AM
To: Manuel Buil <[email protected]>; [email protected]
Subject: RE: Welcome you to try sfc104 demo
Which sfc version are you using? SFC classifier has a bug before I submitted
OVS DPDK enable patch, so you should use sfc master for this demo. In sfc 103
demo, there is only one ACL entry for ping, if I add one more ACL entry for
TCP, SFC classifier can get the correct VxLAN-gpe port. So please switch to SFC
master for this demo.
-----Original Message-----
From: Manuel Buil [mailto:[email protected]]
Sent: Tuesday, November 15, 2016 2:02 AM
To: Yang, Yi Y <[email protected]>; [email protected]
Subject: RE: Welcome you to try sfc104 demo
Hi,
Thanks for the extra information, that was useful!
I found a problem. Inside the classifier1, packets hit the classification rule:
table=0, n_packets=49, n_bytes=3626, priority=1000,tcp,in_port=1,nw_src=192.168.
2.0/24,nw_dst=192.168.2.0/24,tp_dst=80
actions=push_nsh,load:0x1->NXM_NX_NSH_MDTY
PE[],load:0x3->NXM_NX_NSH_NP[],load:0x7f->NXM_NX_NSP[0..23],load:0xff->NXM_NX_NSI
[],load:0x1->NXM_NX_NSH_C1[],load:0x2->NXM_NX_NSH_C2[],load:0x3->NXM_NX_NSH_C3[],
load:0x4->NXM_NX_NSH_C4[],load:0x4->NXM_NX_TUN_GPE_NP[],load:0xc0a83c14->NXM_NX_T
UN_IPV4_DST[],output:1
However, output:1 is 1(veth-br) which is not a vxlan-gpe port and thus the
packet is not encapsulated with vxlan-gpe + nsh. Therefore, the packets which
leave the OVS have the original IP header:
17:36:21.879104 IP 192.168.2.1.43460 > 192.168.2.2.http: Flags [S], seq
1480997927, win 27200, options [mss 1360,sackOK,TS val 413304 ecr 0,nop,wscale
7], length 0
Eth0 does not know where is 192.168.2.2 and its ARP request does not get answer.
I changed that rule to have output:2 which is the vxlan-gpe port. Packets flow
but they don't come back from SF1. I think it might be a problem with the vxlan
tool because I don't see logs coming in /home/vagrant/vxlan_tool.log even
though I can see the packets with tcpdump.
I will try to continue tomorrow as I don't have more time today :(!!
Regards,
Manuel
-----Original Message-----
From: Yang, Yi Y [mailto:[email protected]]
Sent: Saturday, November 12, 2016 3:47 AM
To: Manuel Buil <[email protected]>; [email protected]
Subject: RE: Welcome you to try sfc104 demo
Manuel, good progress, "sudo" is unnecessary.
This indicated sfc didn't create correct flows to SFF1 and SFF2
You can run the below cmds to check every vagrant VMs.
$ source ./env.sh
$ vagrant ssh classifier1
$ vagrant ssh sff1
...
In classifier1, sff1, sff2 and classifier2 vagrant VMs, you can run the below
cmds to check ovs ports, flows.
$ sudo ovs-vsctl show
$ sudo ovs-ofctl -Oopenflow13 dump-flows br-sfc
In sf1 and sf2 VMs, you can run the below cmds to check if SF is running
correctly
$ sudo ps aux | grep vxlan_tool
$ cat /home/vagrant/vxlan_tool.log
In order to check it further, you can run ping and wget in classifier1 and
check where the packet can arrive.
$ vagrant ssh classifier1
$ sudo ip netns exec app ping 192.168.2.2
How do you start your ODL SFC? Another possible reason you run this demo before
SFC features aren't completely started although "feature:list -i | grep sfc"
can see them. I suggest you can make sure ODL SFC is really ready before run
this demo. I'll add such check in run_demo.sh but now it isn't there.
-----Original Message-----
From: Manuel Buil [mailto:[email protected]]
Sent: Saturday, November 12, 2016 1:40 AM
To: Yang, Yi Y <[email protected]>; [email protected]
Subject: RE: Welcome you to try sfc104 demo
Hi Yi yang,
I am having some problems with your demo. I execute " sudo ./run_demo.sh ovs ".
The VMs seems to be created:
$ sudo VBoxManage list runningvms
"sfc104_classifier1_1478856929727_28276" {e41e8e3e-0049-458b-a5f0-e427bdfd6646}
"sfc104_sff1_1478856985216_33607" {4c181ea9-0c6f-4a59-a7ef-7a836dc25d79}
"sfc104_sf1_1478857042513_36221" {f05e13ca-901b-4cac-9446-8da42b2ea5df}
"sfc104_sf2_1478857100191_91163" {c9232419-9fac-4229-b6f2-7dde8afff04e}
"sfc104_sff2_1478857157560_59263" {1bf0ac70-500a-4afa-bc04-84883c098a85}
"sfc104_classifier2_1478857215119_78365" {8affee62-c7e3-483d-bdee-8ac7b4464753}
However, at some point of the script it checks the connectivity and it does not
work:
PING 192.168.2.2 (192.168.2.2) 56(84) bytes of data.
64 bytes from 192.168.2.2: icmp_seq=1 ttl=64 time=11.8 ms
64 bytes from 192.168.2.2: icmp_seq=2 ttl=64 time=8.71 ms
64 bytes from 192.168.2.2: icmp_seq=3 ttl=64 time=11.1 ms
64 bytes from 192.168.2.2: icmp_seq=4 ttl=64 time=9.34 ms
64 bytes from 192.168.2.2: icmp_seq=5 ttl=64 time=9.60 ms
--- 192.168.2.2 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4008ms rtt
min/avg/max/mdev = 8.710/10.138/11.853/1.186 ms Connection to 127.0.0.1 closed.
--2016-11-11 16:58:01-- http://192.168.2.2/ Connecting to 192.168.2.2:80...
failed: Connection timed out.
Retrying.
--2016-11-11 17:00:09-- (try: 2) http://192.168.2.2/ Connecting to
192.168.2.2:80... failed: Connection timed out.
Retrying.
--2016-11-11 17:02:19-- (try: 3) http://192.168.2.2/ Connecting to
192.168.2.2:80... failed: Connection timed out.
Retrying.
--2016-11-11 17:04:29-- (try: 4) http://192.168.2.2/ Connecting to
192.168.2.2:80... failed: Connection timed out.
Retrying.
--2016-11-11 17:06:40-- (try: 5) http://192.168.2.2/ Connecting to
192.168.2.2:80...
Do you know what might be happening?
Thanks,
Manuel
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Yang, Yi Y
Sent: Friday, November 11, 2016 11:47 AM
To: [email protected]
Subject: [sfc-dev] Welcome you to try sfc104 demo
Hi, folks
Brady has merged sfc104 demo into sfc master, so each of you can try sfc104
demo, please let me know if you encounter any issue.
$ cat sfc-demo/sfc104/README.md
SFC104 Demo
===========
Overview
--------
SFC103 demo is docker container based, so you have no way to run it if you will
use OVS DPDK or VPP, so we have to create SFC104 demo, SFC104 demo actually
includes three demos, they are for OVS, OVS DPDK and VPP, respectively.
Your host machine needs 32GB memory at least because DPDK or VPP uses hugepages
which must be allocated in advance, 6 vagrant VMs will occupy 24 GB memory. Too
less memory will result in vagant hang or some other weird behaviors.
Topology
-------
+-----------------+
| Host (ODL SFC) |
| 192.168.60.1 |
+-----------------+
/ | | \
/ | | \
/ | | \
+---------------+ +--------------+ +--------------+ +---------------+
| classifier1 | | sff1 | | sff2 | | classifier2 |
| 192.168.60.10 | |192.168.60.20 | |192.168.60.50 | | 192.168.60.60 |
+---------------+ +--------------+ +--------------+ +---------------+
| |
| |
+---------------+ +--------------+
| sf1(DPI-1) | | sf2(FW-1) |
|192.168.60.30 | |192.168.60.40 |
+---------------+ +--------------+
Setup Demo
----------
1. Install virtualbox & vagrant
2. Start ODL SFC in host machine and install necessary features
1) For ovs or ovs_dpdk
feature:install odl-sfc-scf-openflow odl-sfc-openflow-renderer odl-sfc-ui
2) For vpp
feature:install odl-sfc-vpp-renderer odl-sfc-ui
Notice: please do stop, clean up, then restart ODL SFC when you run this
demo in order that demo can run successfully.
opendaylight-user@root>shutdown -f
opendaylight-user@root>
$ rm -rf data snapshots journal instances
$ ./bin/karaf
3. Run demo
SFC 104 demos will download Ubuntu trusty x86_64 vagrant image and install
all the necessary packages into host and vagrant VMs, so please make sure to
export http_proxy and http_proxy environment variables if you have proxy behind
your network before run demo script, demo script will inject these proxy
settings to vagrant VMS.
1) For OVS demo
$ ./run_demo.sh ovs
2) For OVS DPDK demo
$ ./run_demo.sh ovs_dpdk
3) For VPP demo
$ ./run_demo.sh vpp
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev
_______________________________________________
sfc-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/sfc-dev
