A VPP Configuration Utility

This tool reads a configuration file, checks it for syntax and semantic correctness, and then reconciles a running VPP daemon with its configuration. It is meant to be re-entrant and stateless. The tool connects to the VPP API and creates/removes all of the configuration in a minimally intrusive way.

You can simply install this package from [PyPi]:

$ pip install [--break-system-packages] vppcfg

vppcfg uses the VPP Python API bindings (vpp_papi), which are provided by the python3-vpp-api Debian package that ships with VPP. That copy matches the API of the running dataplane, so it is a prerequisite and is deliberately not pulled in from PyPI (the PyPI copy lags many releases behind and, installed into /usr/local, shadows the deb and breaks API parsing). If you previously installed vpp_papi from PyPI, remove it so the Debian package is used:

$ pip uninstall [--break-system-packages] vpp_papi

Running

usage: vppcfg [-h] [-d] [-q] [-f] {check,dump,plan,apply} ...

positional arguments:
  {check,dump,plan,apply}
    check               check given YAML config for validity (no VPP)
    dump                dump current running VPP configuration (VPP readonly)
    plan                plan changes from current VPP dataplane to target config (VPP readonly)
    apply               apply changes from current VPP dataplane to target config

optional arguments:
  -h, --help            show this help message and exit
  -d, --debug           enable debug logging, default False
  -q, --quiet           be quiet (only warnings/errors), default False
  -f, --force           force progress despite warnings, default False

Please see vppcfg <command> -h   for per-command arguments

Documentation

Main user-focused documentation:

• YAML Configuration Guide
• User Guide

Developer deep-dives:

• Validation
• Path Planning
• Design - Reconciliation

Licensing

The code in this project is released under Apache 2.0 license. A copy of the license is provided in this repo here. All contributions are held against our contributing guidelines. Notably, all code must be licensed Apache 2.0, and all contributions must come with a certificate of origin in the form of a Signed-off-by field in the commit.

All documentation under the docs/ directory is licensed Creative Commons Attribution 4.0 International License (details). A copy of the license is provided in this repo here.