Changes between Version 4 and Version 5 of Documentation/fSDN/bMininet


Ignore:
Timestamp:
Dec 24, 2014, 9:49:44 PM (10 years ago)
Author:
akoshibe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Documentation/fSDN/bMininet

    v4 v5  
    5959[wiki:/Internal/HelloOF see here]
    6060
     61''' Mininet Cluster Edition '''
     62
     63Mininet supports running a network across a set of nodes (cluster). Currently, this relies on SSH tunnels, and is experimental. To enable cluster support, on each node that will be part of the cluster:
     64
     65 1. Generate and exchange SSH keys. If we are running a tiny cluster of node1-1 and node1-2:
     66 {{{
     67ssh-keygen -t rsa
     68ssh-copy-id root@node1-1
     69ssh-copy-id root@node1-2
     70 }}}
     71 Note how a node also has to have its own key in authorized_keys, so we run `ssh-copy-id` against every node in the cluster.
     72
     73 2. Edit ''/etc/ssh/sshd_config'', adding the following two lines:
     74 {{{
     75AllowTCPForwarding yes                                                                               
     76PermitTunnel yes
     77 }}}
     78
     79 3. restart `sshd`
     80 {{{
     81service ssh restart
     82 }}}
     83
     84If all goes well, you should be able to run the following to run a tree topology across nodes1-1 and node1-2:
     85{{{
     86# mn --cluster node1-1,node1-2 --topo tree,2,3
     87}}}
     88
     89The virtual switches are distributed randomly across the two nodes, as indicated as part of the above command's output:
     90{{{
     91*** Placing nodes
     92h1:node1-1 h2:node1-1 h3:node1-1 h4:node1-2 h5:node1-2 h6:node1-2 h7:node1-2 h8:node1-2 h9:node1-2 s1:
     93node1-1 s2:node1-1 s3:node1-2 s4:node1-2
     94}}}
     95
     96If you have a controller running remotely, you can append the ''--controller remote,ip=x.x.x.x'' argument like in a regular `mn` command.
     97
    6198----
    6299''' 1.2.1 Using Wireshark '''[[BR]]