Skip to content

tng bench (osm driver) setup

Avi Mehenwal edited this page Nov 14, 2019 · 19 revisions

This wiki page describes how to install tng-bench and run an demo examples with osm pdriver

Installation

Pre requisits

Installation of tng-bench requires python 3.x installed on system, else further instructions to get python working could be found at their official website.

Also, target machine should have git installed to pull latest tng-bench source

For our purposes we have used and tested installation on ubuntu-18-xenial

Installation Steps

  1. Get the tng-bench source on target machine and make it current working directory.
git clone https://github.com/CN-UPB/tng-sdk-benchmark.git
cd tng-sdk-benchmark
  1. Create a python virtual environment to separate tng-bench python interpreter from system python
python3 -m venv venv
  1. Activate the virtual environment
source venv/bin/activate
  1. Build tng-bench from source
python setup.py install

If all dependencies are installed without fatal errors, we should be good for the next step

  1. Test installation
tng-bench --help

If this generates and output, we can assume that installation went well.

Executing a sample example

Currently, tng-bench comes with a sample ped file which instantiates a minimal network service on openstack using dummy probes.

As of now dummy probes should work fine and we will refine them and update wiki as we make progress.

Make sure all steps from Installation section are followed and virtual environment is activated

From command-line

tng-bench --ped examples-osm/peds/ped_example_vnf.yml --generator osm

Setup vscode to run tng-bench

...

Later ..

During Execution

During execution tng-bench will evaluate the number of experiment configuration based on provided PED file and then try to instantiate those experiments configurations as separated network services one after another in a sequential manner.

If tng-bench execution reaches the Experiment execution stage, we should be able to see the new VNF and NS getting created and destroyed from eithr osm or openstack GUI.

Post execution, all logs and monitoring data collected by prometheus should be captured in results directory

Side notes

  • Using ubuntu images for VNFs prologes the experiment execution time

ToDo

  • Post process monitoring data