Difference between revisions of "VPP Usability Track"

Revision as of 21:46, 6 November 2016

VPP working out of the box for most/all baseline use cases.
Profiled by target VPP consumers - use cases, users.
- Use1 - OPNFV/FDS
- Use2 - Programmable Virtual Forwarder
- Use3 - OpenStack NFVI
- Use4 - vSwitch for VMs

Functional requirements of target VPP consumers - wip - current snapshot:

Use1 - OPNFV/FDS - VXLAN+L2BD+vhost, VLAN+L2BD+vhost, BVI, VRF, IPv4, IPv6, SNAT, ACL/classifier
Use2 - Programmable Virtual Forwarder - VXLAN+L2BD+vhost, IPv4, IPv6, more TBC
Use3 - OpenStack NFVI - VXLAN+L2BD+vhost
Use4 - vSwitch for VMs - VLAN+L2BD+vhost, high-density VNF VMs (30VMs, 102vhost)

Outline of user guide that needs to be produced:

Installation per Linux distro - Ubuntu, Centos, RHEL, other - Ed, Sean
- Packaging
  - https://wiki.fd.io/view/VPP/Installing_VPP_binaries_from_packages#CentOS_7.2_-_VPP_master_branch_RPMs_.28in_development.29
  - sudo yum install vpp-python-api
- Manual install - ??
- Automated install - Ed, Sean
  - see outline in email Ed, Sean "Re: 161026-vpp-usability-review - note", 27 October 2016 at 22:39:47 BST
Environment - MK, FB
- <complete the list of areas and combinations>
- Linux environment fundamentals
- SW Dependencies
  - Linux kernel ver
  - QEMU ver
  - DPDK ver
- HW Dependencies
  - x86_64 microarchitectures
  - NICs
Initial configuration - MK, PM, DM for questions
- Startup configuration - startup.conf ...
- Interfaces
Optimizing VPP performance - MK, PM, PF&DM for questions
- Tuning performance
- VM and vhost-user considerations
- Useful host performance telemetry
- Useful VPP performance telemetry
Sample use cases - Chris Metz with team will work it
- L2 switching
  - with VMs (vhost)
  - with tunnels (vxlan, lisp-gpe)
  - with security-groups
- IP routed forwarding
  - with VMs (vhost)
  - with tunnels (vxlan, lisp-gpe)
  - with security-filters - iacl, cop-whitelist, cop-blacklist
- <add more>
- <structure differently?>
Doc Generation and Online Presentation
- Consider readthedocs approach
  - Based on sphinx using readthedocs theme
  - Used today by dpdk doc

Programmer's guide - KRB for TOC, OT to help

Here initial points to be addressed for optimizing VPP performance on specific compute HW configurations:

cpu core configuration and vpp thread mappings
- phy interfaces can be placed to thread/core
- vhost interfaces are round-robined - new feature for placement
  - do after multi-queue patch by Pierre
vhost - qsz, cpu jitter, reconnect, interop qemu-virtio
- hard to install, doesn't work all the time, crashes
dpdk - performance with selection of NICs
- more detailed documentation about baremetal installations
  - vs. just Vagrant
- dpdk new rls setup recommendations - per NIC basis
- dpdk.org is not publishing performance numbers
- csit can't address it - need manual tests and analysis
vpp self-diagnostics for optimal setup verification

Minimal setup installation for vhost+VM connectivity:

Listing of important areas to increase VPP test coverage:

Following VPP diagnostics and telemetry aspects need to be addressed:

@@ Line 17: / Line 17: @@
 # Use4 - vSwitch for VMs - VLAN+L2BD+vhost, high-density VNF VMs (30VMs, 102vhost)
-==User guide==
+==VPP User Guide - Outline==
-Outline of user guide that needs to be produced:
+Outline of user guide that needs to be produced:
 # Installation per Linux distro - Ubuntu, Centos, RHEL, other - Ed, Sean
 #* Packaging
@@ Line 61: / Line 61: @@
 #** Used today by [http://www.dpdk.org/doc dpdk doc]
-==Programmer's Guide==
+==Programmer's Guide - Outline==
 Programmer's guide - KRB for TOC, OT to help