New feature; now you can specify the placements of hosts as a parameter to Mininet

New feature; now you can specify the placements of hosts as a parameter to Mininet

BUG=

[Michail.Xirouchakis, 2017-09-18 19:42:51]

Please review my code. I have added a new functionality in mininet topology
script. Now you can specify the placement (and number) of hosts as a parameter
to mininet when running from shell. Example:

--topo mytopo,s303,s304,s313,s314 

creates 4 hosts (h1,h2,h3,h4) and attaches them to switches s303,s304,s313 and
s314

[Vasileios Papageorgiou, 2017-09-20 13:45:17]

On 2017/09/18 19:42:51, Michail.Xirouchakis wrote:
> Please review my code. I have added a new functionality in mininet topology
> script. Now you can specify the placement (and number) of hosts as a parameter
> to mininet when running from shell. Example:
> 
> --topo mytopo,s303,s304,s313,s314 
> 
> creates 4 hosts (h1,h2,h3,h4) and attaches them to switches s303,s304,s313 and
> s314


This code sounds more optimal from custom1.py because you can change the txt
file whenever you want to change your topology design. This means that your are
not interfering much with the python code for every single change you make. So,
i believe it is great to use for our topology code that is based on Stanford
figure 1 of project description

[Vasileios Papageorgiou, 2017-09-20 13:51:55]

Topology seems to work properly

[engr.sikandar.iqbal, 2017-09-23 18:00:58]

A test code review

https://codereview.appspot.com/325540043/diff/1/topo-stanford-campus.py
File topo-stanford-campus.py (right):

https://codereview.appspot.com/325540043/diff/1/topo-stanford-campus.py#newco...
topo-stanford-campus.py:22: # creates 4 hosts (h1,h2,h3,h4) and attaches them to
switches s303,s304,s313 and s314
Weldone Michail! it's working for all 4 hosts thanks