Service chains can be a great way to test a great deal of complex functionality in the openNetVM system. The idea is for a program to be written (probably in /examples) that allows for .json configuration file for running different chains of NFs pooled together. We are envisioning a python program that can parse JSON data to start circular or linear chain functionality with different example N

Background

Currently, we can read Ethernet frames with VLAN-tags, but not generate/create ones. We'd like to be able to generate packets with VLAN-tagged Ethernet frames. More information about tags can be found at https://docs.rs/capsule/latest/capsule/packets/struct.Ethernet.html#8021q and https://docs.rs/capsule/latest/capsule/packets/struct.Ethernet.html#8021ad, including links to specs/

While working on another problem (#176), I realized I needed to add changes to kubeadm.cfg while instantiating a cluster. We already do this with the IPv6 deployment, and I can think of a few other things that would be nice to change here too.

I think there are 2 approaches here:

1. Add a template with all the kubeadm options, and build it out with some defaults that can override
2. Provi

As requested bt @kedmison , we beed a README file to explain where diagrams should be kept and include some pointers to how to use .svg files etc.

CI could have differents stages to:

• run style
• run tests
• build documentation

with stages, tests will be runned in parallel and CI should be faster to check commits.

see the travis documentation about stages.

I installed Openbaton on Linux Ubuntu 16.04 using the bootstrap procedure here. I start NFVO service on each startup of my Linux (by adding the line "sudo systemctl start openbaton-nfvo.service" to /etc/rc.local). I can then access Openbaton dashboard GUI by entering http://localhost:8080 in my browser (it redir

pytest 4.x is broke because more-itertools>=6.0.0 dropped python2 support.

Error e.g. def _collate(*iterables, key=lambda a: a, reverse=False):

Reason: pytest-dev/pytest#4770

• https://github.com/sonata-nfv/son-emu/blob/master/Dockerfile#L61
• https://github.com/sonata-nfv/son-emu/blob/master/setup.py#L61
• https://github.com/sonata-nfv/son-emu/blob/mast

OS:Centos7.6
kata-container:1.9.0-alpha1
Nic driver:i40e2.3.2-k
vf driver:i40evf3.2.2-k
According to the community documentation, links to https://github.com/kata-containers/documentation/blob/master/use-cases/using-SRIOV-and-kata.md#install-the-sr-iov-docker-plugin.
Start the container，and perform lspci ,there is no nic deivce inside kata vm.

In the resulting yaml file, we currently only record the number of sources, but not the number of flows they generate or their total data rate.

Both would be quite useful for evaluation and should be easy to add in the result writer. We should add it.