mininet

Files

T

Bob Lantz c3a4440025 Changed custom feature so that params aren't added to globals.

There is probably a better way of doing this, but currently
parseCustomFile can modify globals (e.g. TOPOS) as well as
instance variables (self.validate) and classes (e.g. MyTopo),
which are also in the global name space.

Inconveniently enough, lambdas don't seem to be full closures
in Python; if they were, this trickiness would be unnecessary.

Even so, using execfile() seems like it might be a bit dubious...

2010-02-27 23:19:57 -08:00

custom_example.py

Changed custom feature so that params aren't added to globals.

2010-02-27 23:19:57 -08:00

README

Renamed mn_run.py -> mn, mn_clean.py -> mnclean; updated Makefle

2010-02-03 15:29:07 -08:00

README

This directory should hold configuration files for custom mininets.

See custom_example.py, which loads the default minimal topology.  The advantage of defining a mininet in a separate file is that you then use the --custom option in mn to run the CLI or specific tests with it.

Each custom file must define a Mininet object for an 'mn' variable.

To start up a mininet with this custom topology, do:
  sudo mn --custom custom_example.py