Difference between revisions of "VPP Sandbox/vpp-userdemo"
(Created page with "# INTRO: This is a Vagrant based user demo environment for beginners with VPP The demo requires NodeJS installed on the host (today - we are working dilligently to keep this...") |
|||
Line 6: | Line 6: | ||
You then do the following: | You then do the following: | ||
+ | |||
- install nodeJS from nodejs.org/en/download/ for you host distribution | - install nodeJS from nodejs.org/en/download/ for you host distribution | ||
Revision as of 16:44, 14 September 2016
- INTRO:
This is a Vagrant based user demo environment for beginners with VPP
The demo requires NodeJS installed on the host (today - we are working dilligently to keep this "all in the VM")
You then do the following:
- install nodeJS from nodejs.org/en/download/ for you host distribution
- from folder vpp-userdemo/gui/backend:
npm install
- from folder vpp-userdemo/gui:
NODE_ENV=production node backend/server.js
It walks a user through - each of the commands, - the expected output, - gives a file of the commands used to try themselves
- REQUIREMENTS
- vagrant (1.8) - virtualbox / vmware fusion
- GETTING STARTED
- clone the repo - modify env.sh if needed and ```source ./env.sh``` - by default the VM uses 2 x CPUs and 4G RAM - ```vagrant up``` - ... run the demo
- RUNNING DEMOs
- From the Host, where you ran ```vagrant up``` run ```./run <demoname>```
```./run <demoname>```
- DEMOs
- routing - directly connected routing
- Creates two network namespaces c1, c2 - A gateway interface for each on VPP - Routes due to directly connected routes inserted into default FIB
- bridging - directly connected interfaces into a bridge-domain
- Creates two network namespaces c1, c2 - Adds interfaces to VPP and add them to bridge-domain 1 - MAC addresses are automatically learned
- tracing - how to show a "day in the life of a packet" in VPP
- Same environment as "routing" demo - How to add a trace - View a trace - Interpret a trace