Difference between revisions of "VPP Sandbox/vpp-userdemo"

From fd.io
Jump to: navigation, search
Line 1: Line 1:
# INTRO:
+
= INTRO =
  
 
This is a Vagrant based user demo environment for beginners with VPP
 
This is a Vagrant based user demo environment for beginners with VPP
Line 22: Line 22:
 
- gives a file of the commands used to try themselves
 
- gives a file of the commands used to try themselves
  
# REQUIREMENTS
+
= REQUIREMENTS =
 
- vagrant (1.8)
 
- vagrant (1.8)
 
- virtualbox / vmware fusion
 
- virtualbox / vmware fusion
  
# GETTING STARTED
+
= GETTING STARTED =
 
- clone the repo
 
- clone the repo
 
- modify env.sh if needed and ```source ./env.sh```
 
- modify env.sh if needed and ```source ./env.sh```
Line 33: Line 33:
 
- ... run the demo
 
- ... run the demo
  
# RUNNING DEMOs
+
= RUNNING DEMOs =
 
- From the Host, where you ran ```vagrant up``` run ```./run <demoname>```
 
- From the Host, where you ran ```vagrant up``` run ```./run <demoname>```
  
 
```./run <demoname>```
 
```./run <demoname>```
  
# DEMOs
+
= DEMOs =
  
## routing - directly connected routing
+
== routing - directly connected routing ==
 
- Creates two network namespaces c1, c2
 
- Creates two network namespaces c1, c2
 
- A gateway interface for each on VPP
 
- A gateway interface for each on VPP
 
- Routes due to directly connected routes inserted into default FIB
 
- Routes due to directly connected routes inserted into default FIB
  
## bridging - directly connected interfaces into a bridge-domain
+
== bridging - directly connected interfaces into a bridge-domain ==
 
- Creates two network namespaces c1, c2
 
- Creates two network namespaces c1, c2
 
- Adds interfaces to VPP and add them to bridge-domain 1
 
- Adds interfaces to VPP and add them to bridge-domain 1
 
- MAC addresses are automatically learned
 
- MAC addresses are automatically learned
  
## tracing - how to show a "day in the life of a packet" in VPP
+
== tracing - how to show a "day in the life of a packet" in VPP ==
 
- Same environment as "routing" demo
 
- Same environment as "routing" demo
 
- How to add a trace
 
- How to add a trace
 
- View a trace
 
- View a trace
 
- Interpret a trace
 
- Interpret a trace

Revision as of 16:45, 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