GitLab

this allows this to be called on all networks for mixed experiments.

So far NIC sims would directly modify the NetSim's list, not giving the
opportunity for subclasses to override. This istead adds a method for this.

Useful for running ns-3 only simulations.

Add a new method init_network to NS3E2ENet that does some initialization
before the experiment is run. It should be called after all components
were added to the network.

This introduces the E2ELinkAssigner that can automatically create links
of given types and create all the necessary NS3E2ENet instances.

This adds a new component E2ESimbricksNetwork to the end-to-end
framework, which allows to connect to other simulated networks through
Simbricks.

This avoids issues for parameter strings containing characters that are
treated specially while parsing the arguments, e.g. whitespace.

Instead of passing all parameters using the command line, we write them
first into a file and then pass the filename to the end-to-end
framework.

Use the new basic building blocks SwitchNode and SimpleChannel in the
ns3 end-to-end framework to build topologies.

This adds support for configuring and running simulations using the ns3
end-to-end framework.

Add all TCP congestion control algorithms that are currently available
in the kernel source tree as loadable modules.

This temporarily drops support for DDIO and the L3 cache.

The doc string says to return 1 in the case of an unnecessary sync, which the implementation actually doesn't do. It instead considers an unnecessary sync as success, which is generally also the intended behavior.

We already have a similar and much more detailed section in howto.rst. Further, the included run.py usage print will often be out-of-date and manually updating it every time isn't maintainable.

To manage external links such as for Python Modules, we are now using the extension sphinx.ext.extlinks to define all of them in the file doc/external_links.py.

ExpEnv hd_path and hd_path_raw use absolute path unmodified if given as param

Before this, if registry or tag got set, we would still build all images
starting from the docker hub regsitry version and latest tag.