wiki:GENIExperimenter/ExperimentExample-OF

Version 27 (modified by lnevers@bbn.com, 7 years ago) (diff)

--

GENI OpenFlow Experiment Example 2

This page illustrates an OpenFlow (OF) example for the Omni How-to page. OpenFlow is used for the control of the network resources in the GENI backbone and at Meso-scale campus locations. Experimenters can use GENI resources without learning OpenFlow. Experimenters can choose to control the network switching fabric in their slices by running an OpenFlow controller. Many experimenters use existing OpenFlow controller code as-is, some use controllers with relatively simple modifications, and some experimenters have written their own controller. The GPO is available to help design your controller and plan your experiment configuration. Feel free to contact us at help@geni.net.

The experiment in this page uses Omni from the gcf 1.6.1 package to reserve resources, if you are using gcf 2.0 or higher, note that you must specify the AM API version option -V1 for all Omni commands that are executed at OpenFlow and MyPLC aggregates, these aggregates support AM API V1. The example in this page uses credentials from the GPO ProtoGENI Clearinghouse (pgeni.gpolab.bbn.com) to set up a 3 Meso-scale sites OpenFlow experiment. The sites are BBN, Wisconsin and Clemson each with a MyPLC compute resource. If you are interested in using PG resources, see the HelloGENI experiment page for an OpenFlow experiment using PG nodes.

No image "OF-FOAM-experiment.jpg" attached to GENIExperimenter/ExperimentExample-OF

Omni tools are used to reserve resources in this experiment for each of the site's FlowVisor OpenFlow Aggregate Manager (FOAM) and GENI Aggregate Managers. Steps required to set up this OpenFlow experiment are detailed in this page:

  1. Authentication and Omni tools configuration
  2. Reserve IP Subnet
  3. Determine Resources Availability
  4. Define Compute Resources RSpecs
  5. Define OpenFlow Network Resources RSpecs
  6. Setup Experiment
  7. Run Experiment
  8. Release Resources

The IP Subnet reservation is required for this example experiment because MyPLC resources are used. Also, FOAM sites must be federated in order to trust a Clearinghouse. This is an OpenFlow administrator task that must take place before any of the user OpenFlow operations can take place.

1. Authentication and Omni tools configuration

This example assumes that GENI credentials have been set up as detailed in the GENI Credentials section of the Omni how-to page.

Note: You can use the aggregate_nicknames defined above to specify an aggregate for Omni. The Omni command argument "-a http://myplc.gpolab.bbn.com:12346/" can be replaced by "-a plc-bbn" in any Omni command used below.

A complete list of Aggregate managers is compiled in the GENI Aggregate page, if your site is not listed on this page you should contact your site administrator, or help@geni.net.

2. Reserve GENI IP subnet

In the Meso-scale network a layer 3 experiment requires its own separate IP subnet in order to control all traffic without interfering with traffic from other experiments. Before you start this experiment, you need to request an IP subnet from the gpo-infra@geni.net mail list along with a duration for the subnet reservation. To view the current list of subnets and their current allocation see the GENI Network Core Subnet page. You do not need to request a specific address, one will be chosen for you.

3. Determine Resources Availability

Each of the 3 sites requires an OpenFlow RSpec and a compute resource RSpec. Also, an OpenFlow RSpec is required for the GENI Core (NLR in this example). To find out what resources are available use Omni tools to get a list of available resources from the available aggregates. Following is a list of MyPLC and FOAM aggregates available in the Meso-scale network:

Site MyPLC Aggregate URL MyPLC Aggregate Nickname FOAM Aggregate URL FOAM Aggregate Nickname
BBN http://myplc.gpolab.bbn.com:12346/ plc-bbn https://foam.gpolab.bbn.com:3626/foam/gapi/1 of-bbn
Clemson http://myplc.clemson.edu:12346/ plc-clemson https://foam.clemson.edu:3626/foam/gapi/1 of-clemson
NLR https://foam.nlr.net:3626/foam/gapi/1 of-nlr
Wisconsin https://wings-openflow-1.wail.wisc.edu:12346/ plc-wisconsin https://foam.wail.wisc.edu:3626/foam/gapi/1 of-wisconsin

The experiment captured in this page uses the BBN, Clemson, Wisconsin and NLR aggregates. For a complete list of available GENI aggregates see the GENI Aggregates page. Also, this experiment uses aggregate_nicknames defined in the omni_config to replace the aggregate URLs used by the Omni commands.

4. Define Compute Resources RSpecs

To write a MyPLC RSpec you must determine which nodes will be used for the experiment at each site. This section describes this process, which is comprised of the following steps:

Step 1. Collect listresources from all MyPLC Aggregates.
Step 2. Determine the MyPLC host to be reserved.
Step 3. Generate the MyPLC Rspecs.

Step 1. Collect listresources from all MyPLC Aggregates

As a first step, the experimenter determines the available compute resources at each site. Following are the Omni commands issued to get the advertisements of available compute resources from the BBN, Clemson and Wisconsin MyPLC aggregates:

 $ ./src/omni.py -a plc-bbn listresources -t ProtoGENI 2 -o             # generates rspec-myplc-gpolab-bbn-com-12346-.xml
 $ ./src/omni.py -a plc-clemson listresources -t ProtoGENI 2 -o               # generates rspec-myplc-clemson-edu-12346-.xml
 $ ./src/omni.py -a plc-wisconsin listresources -t ProtoGENI 2 -o  # generates rspec-wings-openflow-1-wail-wisc-edu-12346-.xml

The Omni commands above used the following options:
-t to request the advertisement in V2 RSpec format, the default MyPLc advertisement is in SFA format.
-o argument to get the listresources output into advertisement RSpec files, which are all attached to this page as a reference.

Step 2. Determine the MyPLC hosts to be reserved

From each site's advertisement RSpecs generated above, we choose one host to use in the experiment. Detailed instructions for defining a MyPLC V2 RSpec are available here. This sections shows the MyPLC node details for each site:

BBN MyPLC Host

At the BBN MyPLC, we choose the host navis:

   <node component_id="urn:publicid:IDN+plc:gpolab:gpolab+node+navis.gpolab.bbn.com" 
	component_manager_id="urn:publicid:IDN+plc:gpolab+authority+am" 
	component_name="navis.gpolab.bbn.com" client_id="navis" exclusive="false">
        <sliver_type name="plab-vnode">
        </sliver_type>
    </node>

Clemson MyPLC Host

At the Clemson MyPLC, we choose the host planetlab4:

    <node component_id="urn:publicid:IDN+plc:cu+node+planetlab4.clemson.edu" 
	component_manager_id="urn:publicid:IDN+plc+authority+am" 
	component_name="planetlab4.clemson.edu" client_id="planetlab4" exclusive="false">
        <sliver_type name="plab-vnode">
        </sliver_type>
    </node>

Wisconsin MyPLC Host

At the Wisconsin MyPLC, we choose the host wings-openflow-2:

    <node component_id="urn:publicid:IDN+plc:wisc+node+wings-openflow-2.wail.wisc.edu" 
	component_manager_id="urn:publicid:IDN+plc+authority+am" 
	component_name="wings-openflow-2.wail.wisc.edu" client_id="wings-of2" exclusive="false">
        <sliver_type name="plab-vnode">
        </sliver_type>
    </node>

Step 3. Generate the MyPLCs RSpecs

To generate the MyPLC RSpec, we combine the request V2 RSpec template below with the node details in step 2. Here is the RSpec V2 template:

<?xml version="1.0" ?>
<!-- Resources at AM:
        URN: unspecified_AM_URN
        URL: http://myplc.gpolab.bbn.com:12346/
 -->
<rspec type="request" xmlns="http://www.protogeni.net/resources/rspec/2" 
        xmlns:flack="http://www.protogeni.net/resources/rspec/ext/flack/1" 
        xmlns:planetlab="http://www.planet-lab.org/resources/sfa/ext/planetlab/1" 
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
        xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2 
        http://www.protogeni.net/resources/rspec/2/request.xsd">  

        <!-- Insert MyPLC node details here -->
   
</rspec>

Following are the complete MyPLC RSpecs for each site:

BBN MyPLC Compute Resource RSpec

<?xml version="1.0" ?>
<!-- Resources at AM:
        URN: unspecified_AM_URN
        URL: http://myplc.gpolab.bbn.com:12346/
 -->
<rspec type="request" xmlns="http://www.protogeni.net/resources/rspec/2" 
        xmlns:flack="http://www.protogeni.net/resources/rspec/ext/flack/1" 
        xmlns:planetlab="http://www.planet-lab.org/resources/sfa/ext/planetlab/1" 
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
        xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2 
        http://www.protogeni.net/resources/rspec/2/request.xsd">  
   <node component_id="urn:publicid:IDN+plc:gpolab:gpolab+node+navis.gpolab.bbn.com" 
        component_manager_id="urn:publicid:IDN+plc:gpolab+authority+am" 
        component_name="navis.gpolab.bbn.com" client_id="navis" exclusive="false">
        <sliver_type name="plab-vnode">
        </sliver_type>
    </node>   
</rspec>

Clemson MyPLC Compute Resources RSpec

<?xml version="1.0" ?>
<!-- Resources at AM:
        URN: unspecified_AM_URN
        URL: http://myplc.gpolab.bbn.com:12346/
 -->
<rspec type="request" xmlns="http://www.protogeni.net/resources/rspec/2" 
        xmlns:flack="http://www.protogeni.net/resources/rspec/ext/flack/1" 
        xmlns:planetlab="http://www.planet-lab.org/resources/sfa/ext/planetlab/1" 
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
        xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2 
        http://www.protogeni.net/resources/rspec/2/request.xsd">  
    <node component_id="urn:publicid:IDN+plc:cu+node+planetlab4.clemson.edu" 
        component_manager_id="urn:publicid:IDN+plc+authority+am" 
        component_name="planetlab4.clemson.edu" client_id="planetlab4" exclusive="false">
        <sliver_type name="plab-vnode">
        </sliver_type>
    </node>   
</rspec>

Wisconsin MyPLC Compute Resources RSpec

<?xml version="1.0" ?>
<!-- Resources at AM:
        URN: unspecified_AM_URN
        URL: http://myplc.gpolab.bbn.com:12346/
 -->
<rspec type="request" xmlns="http://www.protogeni.net/resources/rspec/2" 
        xmlns:flack="http://www.protogeni.net/resources/rspec/ext/flack/1" 
        xmlns:planetlab="http://www.planet-lab.org/resources/sfa/ext/planetlab/1" 
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
        xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2 
        http://www.protogeni.net/resources/rspec/2/request.xsd">  
    <node component_id="urn:publicid:IDN+plc:wisc+node+wings-openflow-2.wail.wisc.edu" 
        component_manager_id="urn:publicid:IDN+plc+authority+am" 
        component_name="wings-openflow-2.wail.wisc.edu" client_id="wings-of2" exclusive="false">
        <sliver_type name="plab-vnode">
        </sliver_type>
    </node>
</rspec>

The MyPLC plnodes are pre-configured to use pre-defined addresses; MyPLC doesn't allow experimenters to change that configuration. When the experiment is running you will need to choose the appropriate interface for your experiment traffic based on the IP subnet assigned to you by the GPO infrastructure group as described in the section above.

5. Define OpenFlow Network Resources RSpecs

To write an OpenFlow RSpec you must determine the end-to-end path that will be used for the experiment. This section describes this process, which is comprised of the following steps:

Step 1. Collect listresources from all FOAM Aggregates. Note that these OpenFlow advertisement RSpecs provide insight into all resources at the aggregate, but do not provide any insight into whether they are available.

Step 2. Review GeniAggregate to determine how each experiment MyPLC host maps to the site's OpenFlow switch. Determine addresses and ports, and define site specific OpenFlow packet filter rules.

Step 3. Using guidelines from the Writing OF V3 RSpec page merge the information from Step 2 to generate the request RSpecs.

Each of the above steps is covered in detail below:

Step 1: Collect listresources from all FOAM Aggregate

  1. Clemson FOAM aggregate:
     $ ./src/omni.py -a of-clemson listresources -o    # generates output file rspec-foam-clemson-edu-3626-foam-gapi-1.xml
    
  2. Wisconsin FOAM aggregate:
     $ ./src/omni.py -a of-wisconsin listresources -o  # generates rspec-foam-wail-wisc-edu-3626-foam-gapi-1.xml
    
  3. BBN FOAM aggregate:
     $ ./src/omni.py -a of-bbn listresources -o # generates rspec-foam-gpolab-bbn-com-3626-foam-gapi-1.xml
    
  4. NLR OpenFlow Core FOAM aggregate:
     $ ./src/omni.py -a of-nlr listresources -o        # generates rspec-foam-nlr-net-3626-foam-gapi-1.xml
    

The Omni commands above used the -o argument to get the listresources output into advertisement RSpec files, which are all attached to this page as a reference. The output Advertisement RSpec files provide the switch and the port information to be used in the OpenFlow request RSpec.

Step 2: Determine site specific OpenFlow details

This sections shows you how to determine the site specific OpenFlow RSpec details by walking through the information gathering process. To determine which OpenFlow resources to use, go to the GeniAggregate page and select the OpenFlow Aggregate links for BBN, Clemson and Wisconsin. Each of these OpenFlow Aggregate pages contain a site diagram. The OpenFlow site diagrams show ports, DPIDs, and hosts mapping for the site's OpenFlow switch, which you will have to include in the RSpec. In addition you also have to define how the host traffic will be handled by OpenFlow by defining packet filters. Now, let's map the 3 nodes we chose in the compute resource RSpecs to the appropriate OpenFlow switch ports and determine how they connect to the GENI CORE network VLAN 3715.

BBN OpenFlow Aggregate

To define the OpenFlow request RSpec for the BBN site we need to consider the compute resource we selected, which is the MyPLC node navis.gpolab.bbn.com. We then determine how the node navis is connected to the OpenFlow switch, then we find the Data Path IDentifier (DPID) for the switch VLAN 1750 which is used at every meso-scale site for MyPLC resources to access the backbone OpenFlow VLANs, and finally we determine the path required to connects to the network core OpenFlow VLAN 3715. All this information can be found in the BBN OF Aggregate diagram, which is shown below with the relevant BBN OpenFlow request RSpec details highlighted:

No image "BBNOFAggregateResources.jpg" attached to GENIExperimenter/ExperimentExample-OF

The BBN OpenFlow Aggregate image above shows the information required for the OpenFlow RSpec:

  • Host navis.bbn.com is connected to port name 32 of the OpenFlow switch named habanero
  • OpenFlow switch habanero has a DPID of 06:d6:00:24:a8:c4:b9:00 for VLAN 1750.
  • OpenFlow switch habanero uses port name 47 to connect to port name 20 on the OpenFlow switch poblano.
  • OpenFlow switch poblano has a DPID of 06:d6:00:12:e2:b8:a5:d0 for VLAN 1750.
  • VLAN 1750 is mapped to the Core VLAN 3715 on poblano port name 3.

The BBN habanero OpenFlow switch diagram states that you must add 24 to the port name to determine the port number to use in the RSpec. You do not need to worry about this! The mapping of 'port name' to 'port number' is now done for you by the FOAM aggregate. Simply look for the port names listed above in the listresources output and "borrow" the syntax from the listresources associated to each DPID. Now we know the site specific information and can start to define the BBN OpenFlow resource request RSpec details.

These are the RSpec lines that define the ports on habanero:

  <openflow:group name="bbn-1750-nodes">
    <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+datapath+06:d6:00:24:a8:c4:b9:00"     
                       component_manager_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+authority+am" 
                       dpid="06:d6:00:24:a8:c4:b9:00">
     <openflow:port name="32" num="56"/>
     <openflow:port name="47" num="71"/>
   </openflow:datapath>
 </openflow:group>

These are the RSpec lines that define the ports on poblano:

 <openflow:group name="bbn-1750-3715">
     <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+datapath+06:d6:00:12:e2:b8:a5:d0" 
                        component_manager_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+authority+am" 
                        dpid="06:d6:00:12:e2:b8:a5:d0">
       <openflow:port num="3"/>
        <openflow:port num="20"/>
      </openflow:datapath>
 </openflow:group>

Each OpenFlow RSpec must also include a packet filter definition to describe how the host traffic is to be handled for the experiment. Following is an example packet filter template:

    <openflow:match>
      <openflow:use-group name="group-name" />
      <openflow:packet>
        <openflow:dl_type value="0x800,0x806"/>
        <openflow:nw_dst value="10.42.XX.0/24"/>
        <openflow:nw_src value="10.42.XX.0/24"/>
      </openflow:packet>
    </openflow:match>

Note: The openflow:use-group section of the OpenFlow RSpec defines the traffic characteristics allowed for the experiment.
Note: The group-name should match the openflow:group specific to the OpenFlow switch
Note: The address 10.42.XX.0/24 was requested as described in the section above. Your RSpec will use the subnet you reserved.

For a detailed look at OpenFlow configuration parameters, see the OF V3 RSpec page. On this page you will also find the list of available packet header fields that can be used to filter the OpenFlow traffic.

Let's modify the packet filter definition above so it applies to the BBN OpenFlow resources:

   <openflow:match>

      <openflow:use-group name="bbn-1750-nodes" />
      <openflow:use-group name="bbn-1750-3715" />
      <openflow:packet>
        <openflow:dl_type value="0x800,0x806"/>
        <openflow:nw_dst value="10.42.11.0/24"/>
        <openflow:nw_src value="10.42.11.0/24"/>
      </openflow:packet>

    </openflow:match>

The BBN OpenFlow request RSpec will be completed in Step 3.

Clemson OpenFlow Aggregate

To define the OpenFlow RSpec for the Clemson site review the information in the Clemson OF Aggregate diagram. The compute resource used is the MyPLC node planetlab4.clemson.edu. The following image highlights the the information required from the Clemson OpenFlow Aggregate site diagram:

No image "ClemsonOFAggregateResources.jpg" attached to GENIExperimenter/ExperimentExample-OF

The Clemson OpenFlow Aggregate image above shows the information required for the OpenFlow RSpec:

  • Host planetlab4.clemosn.edu is connected to port name 39
  • The OpenFlow switch had a DPID of 06:d6:00:26:f1:3f:e4:80
  • The site OpenFlow VLAN 1750 is connected to backbone VLAN 3715 on port name 43

These are the lines from the Advertisement that should be used in the OpenFlow request RSpec:

  <openflow:group name="clemson-1750-3715">

     <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam+datapath+06:d6:00:26:f1:3f:e4:80" 
                    component_manager_id="urn:publicid:IDN+openflow:foam:foam+authority+am" dpid="06:d6:00:26:f1:3f:e4:80">
        <openflow:port name="39" num="39"/>
        <openflow:port name="43" num="43"/>
      </openflow:datapath>
  </openflow:group>

In addition packet filters must defined to allow traffic for the IP subnet range reserved for the experiment. Following is the packet filter definitions for Clemson:

   <openflow:match>

      <openflow:use-group name="clemson-1750-3715" />

      <openflow:packet>
	<openflow:dl_type value="0x800,0x806"/>
	<openflow:nw_dst value="10.42.11.0/24"/>
	<openflow:nw_src value="10.42.11.0/24"/>
      </openflow:packet>

    </openflow:match>

The Clemson OpenFlow request RSpec will be completed in Step 3.

Wisconsin OpenFlow Aggregate

To define the OpenFlow RSpec for the Wisconsin site review the Winsconsin OF Aggregate diagram. The compute resource used is the MyPLC node wings-openflow-2.wail.wisc.edu. The Winsconsin OF Aggregate diagram only shows the MAC address for the OpenFlow switch, to determine the DPID simply combine the hexadecimal value for 1750 (06d6) and the MAC address of the switch (00:23:47:CC:44:00) to create the DPID (06:d6:00:23:47:CC:44:00). The following image highlights the the information required from the Wisconsin OpenFlow Aggregate site diagram:

No image "WisconsinOFAggregateResources.jpg" attached to GENIExperimenter/ExperimentExample-OF

The Wisonsin OpenFlow Aggregate image above shows the information required for the OpenFlow RSpec:

  • Host wings-openflow-2.wail.wisc.edu is connected to port name 22.
  • The OpenFlow switch with the hosts has a DPID of 06:d6:00:23:47:cc:44:00
  • The OpenFlow switch with the hosts uses port name 1 to connect to a second switch where VLAN 1750 is mapped to 3715.
  • The second OpenFlow switch has a DPID os 06:d6:00:21:f7:be:8d:00.
  • The second OpenFlow switch uses port nameC3 to map VLAN 1750 to 3715.

Ignore the diagram instructions to add 48 to the C port name on the second OpenFlow switch, this is done for you by FOAM. Simply look for the port names in the listresources output, and borrow the syntax from the listresources associated to each DPID.

These are the lines from the Wisconsin OpenFlow Advertisement that should be used in the OpenFlow request RSpec:

    <openflow:group name="wisconsin-nodes-1750">
      <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.wail.wisc.edu+datapath+06:d6:00:23:47:cc:44:00"
                         component_manager_id="urn:publicid:IDN+openflow:foam:foam.wail.wisc.edu+authority+am">
         <openflow:port name="1" num="1"/>
         <openflow:port name="22" num="22"/>

      </openflow:datapath>
    </openflow:group>

    <openflow:group name="wisconsin-1750-3715">
      <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.wail.wisc.edu+datapath+06:d6:00:21:f7:be:8d:00"
                         component_manager_id="urn:publicid:IDN+openflow:foam:foam.wail.wisc.edu+authority+am">
        <openflow:port name="3" num="3"/>
        <openflow:port name="C3" num="51"/>
      </openflow:datapath>
    </openflow:group>

In addition packet filters are defined to allow traffic for the IP subnet range reserved for the experiment. Following is the packet filter definition for the Wisconsin OpenFlow resources:

    <openflow:match>

      <openflow:use-group name="wisconsin-nodes-1750" />
      <openflow:use-group name="wisconsin-1750-3715" />

      <openflow:packet>
        <openflow:dl_type value="0x800,0x806"/>
        <openflow:nw_dst value="10.42.11.0/24"/>
        <openflow:nw_src value="10.42.11.0/24"/>
      </openflow:packet>

    </openflow:match>

The Wisconsin OpenFlow request RSpec will be completed in Step 3.

NLR OpenFlow Aggregate

To define the NLR OpenFlow RSpec review the OpenFlow DPIDs table for the core in the National LambaRail GENI page. From the table you can see the DPIDs for NLR OpenFlow VLAN 3715. You may choose to use only the two core sites (Chicago and Atlanta) associated with the three experiment sites, but you can also choose to define all DPIDs in the NLR Core for VLAN 3715. This example uses all sites and does not define any port to simplify the experiment workflow. So if you add a site, there is no need to delete, re-create, and re-approved the sliver. Here are the NLR definitions:

   <openflow:group name="nlr-3715">
     <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+datapath+0e:83:00:23:47:c8:bc:00" component_manager_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+authority+am" />
     <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+datapath+0e:83:00:23:47:ca:bc:40" component_manager_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+authority+am" />
     <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+datapath+0e:83:00:24:a8:d2:48:00" component_manager_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+authority+am" />
     <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+datapath+0e:83:00:24:a8:d2:b8:40" component_manager_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+authority+am" />
     <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+datapath+0e:83:00:26:f1:40:a8:00" component_manager_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+authority+am" />
   </openflow:group>

   <openflow:match>
      <openflow:use-group name="nlr-3715" />
      <openflow:packet>
        <openflow:dl_type value="0x800,0x806"/>
        <openflow:nw_dst value="10.42.11.0/24"/>
        <openflow:nw_src value="10.42.11.0/24"/>
      </openflow:packet>
   </openflow:match>

The NLR OpenFlow request RSpec will be completed in Step 3.

Step 3: Generate OpenFlow V3 RSpec

This section uses guidelines from the Writing OF V3 RSpec page to merge information from Step 2 and generate the complete BBN, Clemson, Wisconsin and NLR OpenFlow request RSpecs.

The following OpenFlow V3 RSpec template is used to start each RSpec:

<?xml version="1.1" encoding="UTF-8"?>
<rspec  xmlns="http://www.geni.net/resources/rspec/3"
        xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
        xmlns:openflow="http://www.geni.net/resources/rspec/ext/openflow/3"
        xs:schemaLocation="http://www.geni.net/resources/rspec/3
              http://www.geni.net/resources/rspec/3/request.xsd
              http://www.geni.net/resources/rspec/ext/openflow/3
              http://www.geni.net/resources/rspec/ext/openflow/3/of-resv.xsd"
    type="request">
    
    <openflow:sliver email="user@geni.net" description="OF Experiment" ref="http://www.geni.net">
      <openflow:controller url="tcp:example.geni.net:9933" type="primary" />

        <!-- RSpec details from Step 2 here -->

    </openflow:sliver>
</rspec>

For the above template you must modify the following settings:

  • In the "openflow:sliver" line, replace the "user@geni.net" with your valid email address, and update the sliver description.
  • In the "openflow:controller" line, include your OpenFlow controller name and port information.

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 Setup an OpenFlow Controller. Also, attached to this page is a capture of the OpenFlow Controller software installation, and runtime commands used to run the experiment in this page.

The modified OpenFlow V3 Rspec template is shown below with the setting changes specific to our experiment:

<?xml version="1.1" encoding="UTF-8"?>
<rspec  xmlns="http://www.geni.net/resources/rspec/3"
        xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
        xmlns:openflow="http://www.geni.net/resources/rspec/ext/openflow/3"
        xs:schemaLocation="http://www.geni.net/resources/rspec/3
              http://www.geni.net/resources/rspec/3/request.xsd
              http://www.geni.net/resources/rspec/ext/openflow/3
              http://www.geni.net/resources/rspec/ext/openflow/3/of-resv.xsd"
    type="request">
    
    <openflow:sliver email="lnevers@geni.net" description="OF Experiment" ref="http://www.geni.net">
     <openflow:controller url="tcp:navis.gpolab.bbn.com:33017" type="primary" />

        <!-- RSpec details from Step 2 here -->

    </openflow:sliver>
</rspec>

Using the modified OpenFlow V3 RSpec template we generate the 3 site OpenFlow Rspecs by combining details from Step 2 with the modified template. Following are the completed site OpenFlow RSpecs for the 3 sites in this experiment:

BBN OpenFlow RSpec

<?xml version="1.1" encoding="UTF-8"?>
<rspec  xmlns="http://www.geni.net/resources/rspec/3"
        xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
        xmlns:openflow="http://www.geni.net/resources/rspec/ext/openflow/3"
        xs:schemaLocation="http://www.geni.net/resources/rspec/3
              http://www.geni.net/resources/rspec/3/request.xsd
              http://www.geni.net/resources/rspec/ext/openflow/3
              http://www.geni.net/resources/rspec/ext/openflow/3/of-resv.xsd"
    type="request">
  
<openflow:sliver email="lnevers@geni.net" description="OF Experiment" ref="http://www.geni.net">
   <openflow:controller url="tcp:navis.gpolab.bbn.com:33017" type="primary" />

   <openflow:group name="bbn-1750-nodes">
     <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+datapath+06:d6:00:24:a8:c4:b9:00"     
                       component_manager_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+authority+am" 
                       dpid="06:d6:00:24:a8:c4:b9:00">
      <openflow:port name="32" num="56"/>
      <openflow:port name="47" num="71"/>
    </openflow:datapath>
  </openflow:group>

  <openflow:group name="bbn-1750-3715">
      <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+datapath+06:d6:00:12:e2:b8:a5:d0" 
                        component_manager_id="urn:publicid:IDN+openflow:foam:foam.gpolab.bbn.com+authority+am" 
                        dpid="06:d6:00:12:e2:b8:a5:d0">
        <openflow:port num="3"/>
        <openflow:port num="20"/>
       </openflow:datapath>
  </openflow:group>

  <openflow:match>

      <openflow:use-group name="bbn-1750-nodes" />
      <openflow:use-group name="bbn-1750-3715" />

      <openflow:packet>
        <openflow:dl_type value="0x800,0x806"/>
        <openflow:nw_dst value="10.42.11.0/24"/>
        <openflow:nw_src value="10.42.11.0/24"/>
      </openflow:packet>

   </openflow:match>

 </openflow:sliver>
</rspec>

Clemson OpenFlow RSpec

<?xml version="1.1" encoding="UTF-8"?>
<rspec  xmlns="http://www.geni.net/resources/rspec/3"
        xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
        xmlns:openflow="http://www.geni.net/resources/rspec/ext/openflow/3"
        xs:schemaLocation="http://www.geni.net/resources/rspec/3
              http://www.geni.net/resources/rspec/3/request.xsd
              http://www.geni.net/resources/rspec/ext/openflow/3
              http://www.geni.net/resources/rspec/ext/openflow/3/of-resv.xsd"
    type="request">
    
<openflow:sliver email="lnevers@geni.net" description="OF Experiment" ref="http://www.geni.net">
  <openflow:controller url="tcp:navis.gpolab.bbn.com:33017" type="primary" />

  <openflow:group name="clemson-1750-3715">
     <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam+datapath+06:d6:00:26:f1:3f:e4:80" 
                    component_manager_id="urn:publicid:IDN+openflow:foam:foam+authority+am" dpid="06:d6:00:26:f1:3f:e4:80">
        <openflow:port name="39" num="39"/>
        <openflow:port name="43" num="43"/>
      </openflow:datapath>
  </openflow:group>

  <openflow:match>
      <openflow:use-group name="clemson-1750-3715" />
      <openflow:packet>
        <openflow:dl_type value="0x800,0x806"/>
        <openflow:nw_dst value="10.42.11.0/24"/>
        <openflow:nw_src value="10.42.11.0/24"/>
      </openflow:packet>
    </openflow:match>

</openflow:sliver>
</rspec>

Wisconsin OpenFlow RSpec

<?xml version="1.1" encoding="UTF-8"?>
<rspec  xmlns="http://www.geni.net/resources/rspec/3"
        xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
        xmlns:openflow="http://www.geni.net/resources/rspec/ext/openflow/3"
        xs:schemaLocation="http://www.geni.net/resources/rspec/3
              http://www.geni.net/resources/rspec/3/request.xsd
              http://www.geni.net/resources/rspec/ext/openflow/3
              http://www.geni.net/resources/rspec/ext/openflow/3/of-resv.xsd"
    type="request">
    
<openflow:sliver email="lnevers@geni.net" description="OF Experiment" ref="http://www.geni.net">
  <openflow:controller url="tcp:navis.gpolab.bbn.com:33017" type="primary" />

   <openflow:group name="wisconsin-nodes-1750">
      <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.wail.wisc.edu+datapath+0
6:d6:00:23:47:cc:44:00"
                         component_manager_id="urn:publicid:IDN+openflow:foam:foam.wail.wisc.edu+au
thority+am">
          <openflow:port name="1" num="1"/>
          <openflow:port name="22" num="22"/>

      </openflow:datapath>
   </openflow:group>

   <openflow:group name="wisconsin-1750-3715">
      <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.wail.wisc.edu+datapath+0
6:d6:00:21:f7:be:8d:00"
                         component_manager_id="urn:publicid:IDN+openflow:foam:foam.wail.wisc.edu+au
thority+am">
        <openflow:port name="3" num="3"/>
        <openflow:port name="C3" num="51"/>
      </openflow:datapath>
   </openflow:group>

   <openflow:match>
      <openflow:use-group name="wisconsin-nodes-1750" />
      <openflow:use-group name="wisconsin-1750-3715" />
      <openflow:packet>
        <openflow:dl_type value="0x800,0x806"/>
        <openflow:nw_dst value="10.42.11.0/24"/>
        <openflow:nw_src value="10.42.11.0/24"/>
      </openflow:packet>
    </openflow:match>


</openflow:sliver>
</rspec>

NLR OpenFlow RSpec

<?xml version="1.1" encoding="UTF-8"?>
<rspec  xmlns="http://www.geni.net/resources/rspec/3"
        xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
        xmlns:openflow="http://www.geni.net/resources/rspec/ext/openflow/3"
        xs:schemaLocation="http://www.geni.net/resources/rspec/3
              http://www.geni.net/resources/rspec/3/request.xsd
              http://www.geni.net/resources/rspec/ext/openflow/3
              http://www.geni.net/resources/rspec/ext/openflow/3/of-resv.xsd"
    type="request">
    
<openflow:sliver email="lnevers@geni.net" description="OF Experiment" ref="http://www.geni.net">
  <openflow:controller url="tcp:navis.gpolab.bbn.com:33017" type="primary" />

   <openflow:group name="nlr-3715">
     <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+datapath+0e:83:00:23:47:c8:bc:00" component_manager_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+authority+am" />
     <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+datapath+0e:83:00:23:47:ca:bc:40" component_manager_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+authority+am" />
     <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+datapath+0e:83:00:24:a8:d2:48:00" component_manager_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+authority+am" />
     <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+datapath+0e:83:00:24:a8:d2:b8:40" component_manager_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+authority+am" />
     <openflow:datapath component_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+datapath+0e:83:00:26:f1:40:a8:00" component_manager_id="urn:publicid:IDN+openflow:foam:foam.nlr.net+authority+am" />
   </openflow:group>

   <openflow:match>
      <openflow:use-group name="nlr-3715" />
      <openflow:packet>
        <openflow:dl_type value="0x800,0x806"/>
        <openflow:nw_dst value="10.42.11.0/24"/>
        <openflow:nw_src value="10.42.11.0/24"/>
      </openflow:packet>
   </openflow:match>
</openflow:sliver>
</rspec>

6. Setup Experiment

Using 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 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:

 $ cd gcf-1.6.1
 $ ./src/omni.py createslice 3sites-OF
 $ ./src/omni.py -a of-bbn createsliver 3sites-OF openflow-bbn.rspec
 $ ./src/omni.py -a of-clemson createsliver 3sites-OF openflow-clemson.rspec   
 $ ./src/omni.py -a of-wisconsin createsliver 3sites-OF openflow-wisconsin.rspec
 $ ./src/omni.py -a of-nlr createsliver 3sites-OF openflow-nlr.rspec
 $ ./src/omni.py -a plc-bbn createsliver 3sites-OF myplc-bbn.rspec 
 $ ./src/omni.py -a plc-clemson createsliver  3sites-OF  myplc-clemson.rspec
 $ ./src/omni.py -a plc-wisconsin createsliver 3sites-OF myplc-wisconsin.rspec
                   

The output for running each of the above commands is attached here. Also each of the RSpecs used to create slivers are also attached to this page.

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 Omni sliverstatus commands. Following are the commands to determine the current sliverstatus along with the expiration times at each aggregate:

 $ ./src/omni.py -a of-bbn sliverstatus 3sites-OF
 $ ./src/omni.py -a of-clemson sliverstatus 3sites-OF
 $ ./src/omni.py -a of-wisconsin sliverstatus 3sites-OF
 $ ./src/omni.py -a of-nlr sliverstatus 3sites-OF
 $ ./src/omni.py -a plc-clemson sliverstatus 3sites-OF
 $ ./src/omni.py -a plc-wisconsin  sliverstatus 3sites-OF
 $ ./src/omni.py -a plc-bbn sliverstatus 3sites-OF

The output for running each of the above commands is attached here.

You can now renew the slice and slivers. Following are the commands to extend the reservation for the resources:

 $ ./src/omni.py renewslice  3sites-OF 2012-04-30
 $ ./src/omni.py -a of-bbn renewsliver 3sites-OF 2012-04-30
 $ ./src/omni.py -a of-clemson renewsliver 3sites-OF 2012-04-30
 $ ./src/omni.py -a of-wisconsin renewsliver 3sites-OF 2012-04-30
 $ ./src/omni.py -a of-nlr renewsliver 3sites-OF 2012-04-30
 $ ./src/omni.py -a of-clemson renewsliver 3sites-OF 2012-04-30
 $ ./src/omni.py -a of-wisconsin  renewsliver 3sites-OF 2012-04-30
 $ ./src/omni.py -a of-bbn renewsliver 3sites-OF 2012-04-30

The output for running each of the above renew commands is attached here.

FOAM sliver approval

Each of the OpenFlow slivers must be approved by an administrator at each of the OpenFlow Aggregates. You do not need to take any action, an email notification will be sent for each of the FOAM aggregates that looks as follows:

No image "FOAM-sliver-approve.jpg" attached to GENIExperimenter/ExperimentExample-OF

In the scenario captured in this page, there are 4 sliver approval notifications, one from each of the FOAM aggregates (BBN, Clemson, NLR and Wisconsin).

7. Run Experiment

Once your flowspace has been approved, 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 help@geni.net.

Login to a MyPLC host

To figure out how to login to the MyPLC hosts that you reserved use the Omni sliverstatus commands. Following are examples for the experiment captured in this page:

 $ ./src/omni.py -a plc-clemson sliverstatus 3sites-OF
 $ ./src/omni.py -a plc-bbn sliverstatus 3sites-OF 
 $ ./src/omni.py -a plc-wisconsin sliverstatus 3sites-OF

The output for running each of the above sliverstatus commands is attached here.

From 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:

MyPLC Site Login (pl_login) MyPLC Host (pl_hostname) Command to connect
BBN pgenigpolabbbncom_3sitesOF navis.gpolab.bbn.com ssh pgenigpolabbbncom_3sitesOF@navis.gpolab.bbn.com
Clemson pgenigpolabbbncom_3sitesOF planetlab4.clemson.edu ssh pgenigpolabbbncom_3sitesOF@planetlab4.clemson.edu
Wisconsin pgenigpolabbbncom_3sitesOF wings-openflow-2.wail.wisc.edu ssh pgenigpolabbbncom_3sitesOF@wings-openflow-2.wail.wisc.edu

Login 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:

$ ssh pgenigpolabbbncom_3sitesOF@navis.gpolab.bbn.com
Last login: Fri Apr 20 15:22:13 2012 from sendaria.gpolab.bbn.com
[pgenigpolabbbncom_3sitesOF@navis ~]$ /sbin/ifconfig |egrep "10.42.11\." -A 1 -B 1
eth1.1750:42011 Link encap:Ethernet  HWaddr 00:1B:21:5A:E6:A9  
          inet addr:10.42.11.55  Bcast:10.42.11.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

You should verify connectivity between the MyPLC hosts before running your experiment. The following example show connectivity from BBN host navis to Clemson host planetlab4:

[pgenigpolabbbncom_3sitesOF@navis ~]$ ping 10.42.11.104 -c 3
PING 10.42.11.104 (10.42.11.104) 56(84) bytes of data.
64 bytes from 10.42.11.104: icmp_seq=1 ttl=64 time=59.3 ms
64 bytes from 10.42.11.104: icmp_seq=2 ttl=64 time=59.3 ms
64 bytes from 10.42.11.104: icmp_seq=3 ttl=64 time=59.3 ms

--- 10.42.11.104 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2006ms
rtt min/avg/max/mdev = 59.327/59.337/59.354/0.199 ms
[pgenigpolabbbncom_3sitesOF@navis ~]$ 

and from Wisconsin host wings-openflow-2 to Clemson host planetlab4:

[pgenigpolabbbncom_3sitesOF@wings-openflow-2 ~]$ ping 10.42.11.104 -c 3
PING 10.42.11.104 (10.42.11.104) 56(84) bytes of data.
64 bytes from 10.42.11.104: icmp_seq=1 ttl=64 time=40.6 ms
64 bytes from 10.42.11.104: icmp_seq=2 ttl=64 time=40.6 ms
64 bytes from 10.42.11.104: icmp_seq=3 ttl=64 time=40.6 ms

--- 10.42.11.104 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2044ms
rtt min/avg/max/mdev = 40.610/40.652/40.699/0.168 ms

You can now run an experiment!

8. Release Resources

When 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:

./src/omni.py -a of-bbn deletesliver 3sites-OF
./src/omni.py -a of-clemson deletesliver 3sites-OF
./src/omni.py -a of-wisconsin deletesliver 3sites-OF
./src/omni.py -a of-nlr deletesliver 3sites-OF
./src/omni.py -a plc-clemson deletesliver  3sites-OF 
./src/omni.py -a plc-wisconsin deletesliver 3sites-OF
./src/omni.py -a plc-bbn deletesliver 3sites-OF 


Email help@geni.net for GENI support or email me with feedback on this page!

Attachments (10)

Download all attachments as: .zip