Cluster edition prototype: remote nodes and links.
We add a new experimental feature to allow Mininet to run across a cluster of machines. This is currently implemented via a set mix-in classes that provide remote nodes that are implemented via a connection to a remote shell, and remote links which are tunnels across servers. In this preliminary implementation, both control and data connections are made via ssh, but this could change in the future. A MininetCluster class is provided which allows existing code to be used with minimal modification - all that is required is to provide a list of servers to use. A customizable placement algorithm may also be specified. An experimental CLI subclass is also provided to make it easier to examine node placement; status and links commands can also check whether nodes and tunnels are still running. Although this is an experimental feature, it does include a --cluster option to make it convenient to start up a Mininet simulation over a cluster, and a script to assist with setting up the prerequisite authentication via ssh key pairs. The cluster feature is preliminary and missing some obvious important features, such as parallel startup and multiple tunnel types, which we hope to add in the future.
Showing
- bin/mn 36 additions, 3 deletionsbin/mn
- examples/cluster.py 831 additions, 0 deletionsexamples/cluster.py
- examples/clustercli.py 93 additions, 0 deletionsexamples/clustercli.py
- examples/clusterdemo.py 23 additions, 0 deletionsexamples/clusterdemo.py
- mininet/clean.py 21 additions, 12 deletionsmininet/clean.py
- mininet/cli.py 6 additions, 1 deletionmininet/cli.py
- mininet/link.py 46 additions, 23 deletionsmininet/link.py
- mininet/net.py 9 additions, 1 deletionmininet/net.py
- mininet/node.py 35 additions, 23 deletionsmininet/node.py
- mininet/util.py 12 additions, 15 deletionsmininet/util.py
- util/clustersetup.sh 182 additions, 0 deletionsutil/clustersetup.sh
Loading
Please register or sign in to comment