Carmelo Cascone b4e61e9b1b Remove depenency on internal BMv2 device ID when starting bmv2.py
Needed to support TestON-based Segment Routing tests. All instances
started with internal ID = 0 (one PI/P4Runtime server procees is
executed for each simple_switch_grpc instance, i.e, there's no need to
use different internal IDs to distinguish between switch instances).
Log/conf files and bm-* commands are now based on switch name.

Change-Id: I34d3079d6dff5933ceb4d95f04863426af24eb81
2018-05-24 13:37:00 -07:00
..
2016-09-12 17:56:20 +00:00
2016-09-07 23:07:11 +00:00

Mininet dev tools README

This directory contains modules for Mininet that are
intended to help with ONOS core and application development.

They can be imported into Python scripts, or invoked using
mn's --custom option.

Test topologies for use with Mininet may be found in
../../test/topos


onos.py:

onos.py provides a Mininet controller class which makes it
convenient to create ONOS clusters in a single VM. It also
creates a customizable control network. Additional information
may be found in the module comment and on the docs wiki.

example: sudo mn --custom onos.py --controller onos,1 --topo linear,10


bmv2.py:

bmv2.py provides a Mininet switch class which enables use of
the BMv2 P4 software switch.

Additional information may be found on the docs wiki.


examples/:

The examples/ directory contains example scripts which may make
use of onos.py or other modules in this directory.