Skip to content

Commit f66e9e3

Browse files
author
Steven Van Rossem
committed
2 parents e6a0ef3 + 3ba18c1 commit f66e9e3

3 files changed

Lines changed: 44 additions & 3 deletions

File tree

demo_SDK_IEEE_SDNNFV2017/README.md

Lines changed: 44 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -89,10 +89,51 @@ If the X11 settings are correct, a plot figure will show the ongoing profiling m
8989

9090
#### Demo VM example services
9191

92-
* **ovs_and_ryu**: Openflow switch VNF (ovs) with a controller VNF (Ryu)
93-
* vEPC: to illustrate the editor and validator tools, different versions of a vEPC service are demonstrated. The increased complexity of the service graphs shows the added value of a formal validation tool.
92+
* **ovs_and_ryu**: Openflow switch VNF (ovs) with a controller VNF (Ryu).
93+
Check the deployment movie [on youtube](https://www.youtube.com/watch?v=J14mb79Fwmc&t=445s)
94+
95+
* **vEPC**: to illustrate the editor and validator tools, different versions of a vEPC service are demonstrated. The increased complexity of the service graphs shows the added value of a formal validation tool.
9496
* **vepc**: The normal vEPC service, with MME, HSS, SGW, PGW and one VDU per VNF
9597
* **vepc_scaled**: The scaled version of the vEPC, where the VNF (MME, SGW, PGW) is scaled out with multiple VDUs (including a load-balancer and a datastore). The scaled VNFs are seen in the validator web gui, when opening VDU view.
9698
* **vepc_scaled_mgmt**: A management network is added to the previous vEPC service, to show the increased complexity and difficulty for graph validation.
9799
* **vepc_error**: An error is introduced in the previous vEPC version, the errors/warnings are listed in the validator web gui.
98-
* vCDN: to be added
100+
101+
* **vCDN**: This example service deploys a 3 pop topology. The vCDN service consists out of a webserver and multiple vCaches (squid VNFs). The emulated service can be manipulated to deploy vCache VNFs closer to the users if needed.
102+
This illustrates the SDK ability to:
103+
* Test different placement strategies
104+
* Manipulate the chaining (SFC) of the deployed service
105+
* Test different scaling strategies and monitor their effects
106+
The scripts needed for the SSM/FSM (for service or VNF configuration or scaling can be tested this way)
107+
108+
The commands to be used for the vCDN service:
109+
```
110+
# deploy the test topology in the emulator (use a different terminal)
111+
sudo python src/emuvim/examples/demo_topo_3pop_vcdn.py
112+
113+
# push the package for deployment (directly via the REST api)
114+
cd /demo_services/vcdn
115+
curl --fail -i -X POST -F package=@vcdn.son http://127.0.0.1:5000/packages
116+
# or push from the editor at http://localhost:8080
117+
118+
# configure the VNFs
119+
cd /demo_services/vcdn
120+
son-exec vCDN-SAP1 configure_sap1_start.sh
121+
son-exec vCDN-SAP2 configure_sap2_start.sh
122+
123+
# start monitoring (check Grafana at: http://localhost:3000 )
124+
sudo son-monitor msd -f msd2.yml
125+
126+
# check the dashboard at: http://localhost:5001/dashboard/index.html
127+
128+
# add another vCache VNF (squid), closer to the vCDN-users2
129+
source scale_out.sh
130+
131+
# check the dashboard if a second VNF (squid2) has been placed
132+
# check Grafana if traffic is routed to squid2
133+
134+
# scale back in
135+
source scale_in.sh
136+
137+
# check the dashboard if a second VNF (squid2) has been removed
138+
# check Grafana if traffic is routed back to squid1
139+
```
1.03 MB
Binary file not shown.
1.26 MB
Binary file not shown.

0 commit comments

Comments
 (0)