Changes between Version 23 and Version 24 of GEC13Agenda/ExperimenterWorkflowTutorial/Tutorial

Timestamp:

03/13/12 01:38:33 (13 years ago)

Author:

nriga@bbn.com

Comment:

--

GEC13Agenda/ExperimenterWorkflowTutorial/Tutorial

@@ -815 +815 @@
 == 1. Make an OpenFlow sliver ==
 
-In the previous step, we have used a pre-configured setup to run our test. In
-this experiment we will first reserve an OpenFlow sliver that will point to a
-controller to control our traffic.
+In the previous step, we have used a pre-configured setup to run our test. We have reserved OpenFlow slivers and we are running some default controllers to route the packets for the above subnets and ethernet types. In this experiment you will reserve an OpenFlow sliver and point it to a controller to route your traffic. For the tutorial purposes we are already running the controller for you. The only thing you will have to do is point your OpenFlow sliver to the running controller. 
 
 === 1a. !OpenFlow controller ===
@@ -825 +823 @@
 the controllers that are running on a myPlc host at GPO. 
 
-In the previous example we have pointed all the traffic for subnets
-10.42.144.0/24, 10.42.149.0/24 to a switch !OpenFlow controller, that's why you
-were able to ping between your hosts, using that subnet. 
+In the previous example we have pointed the slivers for subnets 10.42.144.0/24 and 10.42.149.0/24 to an !OpenFlow controller that acts like a layer 2 switch. This is why you were able to ping between your hosts.
 
 === 1b. !OpenFlow sliver ===
-Until you have reserved an !OpneFlow sliver, traffic would not be forwarded
-between your hosts on your assigned subnet.
+Until you have reserved an !OpenFlow sliver, traffic will not be forwarded between your hosts on your assigned subnet.
 
 Try pinging between the myPlc hosts from Exercise II but using the subnet that has been assigned to you. 
@@ -839 +834 @@
 }}}
  
-Since there is OpenFlow sliver configured yet to forward packets in your subnet, ping should fail. 
-
-'''Ask us to give a slip of paper with the information about your OpenFlow sliver.'''
-
-   * Personalize your rspec. There is a sample !OpenFlow rspec, under the rspecs
-folder ('''rspecs/openflow-tutorial-template.rspec'''), that you would need to
-modify in order to reserve the flowspace that has been assigned to you. In the
-beginning of the file there is a list of tags you would need to replace. More
-specifically
-       * <USERNAME> : Your usernamer
+Since there is no OpenFlow sliver configured yet to forward packets in your subnet, ping should fail. 
+
+'''Ask us to give you a slip of paper with the information about your OpenFlow sliver.'''
+
+   * Personalize your rspec. There is a sample !OpenFlow rspec, under the rspecs folder ('''rspecs/openflow-tutorial-template.rspec'''), that you would need to modify in order to reserve the flowspace that has been assigned to you. In the beginning of the file there is a list of tags you would need to replace. More specifically
+       * <USERNAME> : Your username
        * <CTRL-PORT> : The port that your controller will be listening on on
 navis.gpolab.bbn.com
@@ -857 +848 @@
 you for use in this exercise
 
-   * Create the OpenFlow sliver. The flowspace for the tutorial is managed by an
-AM running at GPO :
-   {{{
-   omni.py createsliver gposliceXX ./rspecs/openflow-tutorial-template.rspec -a
-of-tut
+   * Create the OpenFlow sliver. The flowspace for the tutorial is managed by a central AM running at GPO :
+   {{{
+   omni.py createsliver gposliceXX ./rspecs/openflow-tutorial-template.rspec -a of-tut
    }}}