Changes between Version 84 and Version 85 of GENIExperimenter/ExperimentExample-OF-FOAM


Ignore:
Timestamp:
04/20/12 11:26:52 (8 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/ExperimentExample-OF-FOAM

    v84 v85  
    402402 * In the "openflow:controller" line, include your !OpenFlow controller name and port information.
    403403
    404 Note: If you do not have an !OpenFlow controller, you can set one up as shown [http://groups.geni.net/geni/wiki/OpenFlow/GeniBackboneTest#SetupyourOpenFlowcontroller here].
     404''Note:'' You must run an !OpenFlow Controller to manage your experiment. If you do not have an !OpenFlow controller, see the following page for instructions on how-to [http://groups.geni.net/geni/wiki/OpenFlow/GeniBackboneTest#SetupyourOpenFlowcontroller Setup an OpenFlow Controller].  Also, attached to this page is a [http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/ExperimentExample-OF-FOAM/nox-install.txt capture] of the !OpenFlow Controller software installation, and runtime commands used to run the experiment in this page.
    405405
    406406The modified !OpenFlow V3 Rspec template is shown below with the setting changes specific to our experiment:
     
    613613
    614614
    615 == Create Slice and Request Resources ==
    616 
    617 Using the RSpecs that define the OF flowspace and compute resource for our experiment, we can now set up the experimennt with Omni. First create a slice using your GPO Clearinghouse credentials as defined in the omni_config. Note that the slice name should be meaningful to you and then create a sliver for each resource aggregate.  In this example there are 4 OF aggregates (one per site plus one for the GENI core) and 3 compute resource aggregates (3 MyPLC), which maps to creating 7 slivers, and the following commands are executed:  XXXX
     615== Setup Experiment ==
     616
     617Using the !OpenFLow and compute resource RSpecs we defined above, we can now set up an experimennt with Omni. First, we create a slice using the GPO Clearinghouse credentials as defined in the [wiki:GENIExperimenter/ExperimentExample-OF-FOAM#AuthenticationandOmnitoolsconfiguration Omni configuration]. Note, you should choose a slice name that is meaningful to you. Then, we create a sliver for each resource aggregate.  In this example there are 4 !OpenFlow aggregates (one per site plus one for the GENI core) and 3 compute resource aggregates (3 MyPLC), which maps to creating 7 slivers. The following commands are executed to set up the experiment: 
    618618{{{
    619619 $ cd gcf-1.6.1
     
    631631The output for running each of the above commands is attached [http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/ExperimentExample-OF-FOAM/openflow-foam-example.txt here].
    632632
    633 Remember, to renew the slice and slivers reservation time, as the default time is 8 hours. You may find out the current expiration time by using sliverstatus with the Omni tools. Following are the commands to determine the current sliverstatus along with expiration time:
     633Remember, to renew the slice and slivers reservation time, as the default time is 8 hours. You may find out the current expiration time by using Omni sliverstatus commands. Following are the commands to determine the current sliverstatus along with the expiration times at each aggregate:
    634634{{{
    635635./src/omni.py -a https://foam.gpolab.bbn.com:3626/foam/gapi/1 sliverstatus 3sites-OF-Exp
     
    644644
    645645
    646 You can now renew the slice and slivers, following are the commands to extend the reservation for the resources:
     646You can now renew the slice and slivers. Following are the commands to extend the reservation for the resources:
    647647{{{
    648648 $ ./src/omni.py renewslice  3sites-OF-Exp 2012-04-27
     
    658658The output for running each of the above renew commands is attached [http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/ExperimentExample-OF-FOAM/openflow-foam-renew.txt here].
    659659
    660 === Setup an OpenFlow Controller for the Experiment ===
    661 
    662 Once you have set up your resources you need to install and run an !OpenFlow Controller to manage your experiment. See the following page for instructions to [http://groups.geni.net/geni/wiki/OpenFlow/GeniBackboneTest#SetupyourOpenFlowcontroller Setup an OpenFlow Controller].  Also, attached is a [http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/ExperimentExample-OF-FOAM/nox-install.txt capture] of the !OpenFlow Controller software installation, and how the controller is run for this example.
    663660
    664661=== FOAM sliver approval ===
     
    672669== Run Experiment ==
    673670
    674 Once your flowspace has been opted in you should be able login to each of the MyPLC hosts and exchange traffic over the approved flows between the hosts that have been allocated to your experiment.  Simply SSH into one of the hosts and ping any of the other hosts to verify connectivity. If you have connectivity between the allocated hosts, you may start your experiment, if you do not have connectivity, contact [mailto:help@geni.net].
     671Once your flowspace has been opted in, you should be able login to each of the MyPLC hosts and exchange traffic over the approved flows.  Simply SSH into one of the hosts and ping any of the other hosts to verify connectivity. If you have connectivity between the allocated hosts, you may start your experiment, if you do not have connectivity, contact [mailto:help@geni.net].
    675672
    676673=== Login to a MyPLC host ===
     
    685682The output for running each of the above sliverstatus commands is attached [http://groups.geni.net/geni/attachment/wiki/GENIExperimenter/ExperimentExample-OF-FOAM/sliverstatus-3sites-OF-Exp.txt here].
    686683
    687 From the output of the sliverstatus, we use the ''pl_login'' and the ''pl_hostname'' to ssh into the MyPLC hosts:
     684From the output of the sliverstatus commands, we use the ''pl_login'' and the ''pl_hostname'' to ssh into the MyPLC hosts. Following is a summary for the sites in this experiment:
    688685
    689686|| MyPLC Site || Login (pl_login)           || MyPLC Host (pl_hostname) || Command to connect ||
     
    696693
    697694
    698 Login to each of the 3 hosts and determine the host's address for the 10.42.11.0/24 network. Note this is the network that was configured in the OpenFlow groups.  In this scenario the BBN host is 10.42.11.55, the Clemson host is 10.42.11.104, and the Wisconsin host is ????
    699 
     695Login to each of the 3 hosts to determine the host address for the network 10.42.11.0/24, which is the network reserved and configured for the !OpenFlow groups.  Here is an example for the node navis:
     696{{{
     697$ ssh pgenigpolabbbncom_3sitesOFExp@navis.gpolab.bbn.com
     698Last login: Fri Apr 20 15:22:13 2012 from sendaria.gpolab.bbn.com
     699[pgenigpolabbbncom_3sitesOFExp@navis ~]$ /sbin/ifconfig |egrep "10.42.11\." -A 1 -B 1
     700eth1.1750:42011 Link encap:Ethernet  HWaddr 00:1B:21:5A:E6:A9 
     701          inet addr:10.42.11.55  Bcast:10.42.11.255  Mask:255.255.255.0
     702          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
     703}}}
     704
     705You should verify connectivity between the MyPLC hosts before running your experiment. The following example show connectivity from BBN host navis to Clemson host planetlab4:
     706{{{
     707[pgenigpolabbbncom_3sitesOFExp@navis ~]$ ping 10.42.11.104 -c 3
     708PING 10.42.11.104 (10.42.11.104) 56(84) bytes of data.
     70964 bytes from 10.42.11.104: icmp_seq=1 ttl=64 time=59.3 ms
     71064 bytes from 10.42.11.104: icmp_seq=2 ttl=64 time=59.3 ms
     71164 bytes from 10.42.11.104: icmp_seq=3 ttl=64 time=59.3 ms
     712
     713--- 10.42.11.104 ping statistics ---
     7143 packets transmitted, 3 received, 0% packet loss, time 2006ms
     715rtt min/avg/max/mdev = 59.327/59.337/59.354/0.199 ms
     716[pgenigpolabbbncom_3sitesOFExp@navis ~]$
     717}}}
     718
     719You can now use the hosts to run an experiment!
    700720
    701721== Release Resources ==
    702722
    703 When the experiment is completed you should release the resources by deleting the sliver for each of the Resource Aggregates used in the Experiment. In the example experiment used in this page, the following commands should be issued to release resources:
     723When the experiment is completed, you should release the resources by deleting the sliver for each of the resource aggregates in the Experiment. In the example experiment in this page, the following commands should be issued to release resources:
    704724{{{
    705725./src/omni.py -a https://foam.gpolab.bbn.com:3626/foam/gapi/1 deletesliver 3sites-OF-Exp