Changes between Version 1 and Version 2 of GENIExperimenter/ExperimentExample-OF-FOAM


Ignore:
Timestamp:
04/02/12 11:31:57 (12 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

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

    v1 v2  
    33= GENI !OpenFlow Experiment Example 2 =
    44
    5 This page illustrates an operational !OpenFlow (OF) example for the [wiki:HowToUseOmni Omni How-to] page. [http://www.openflow.org/ OpenFlow] is used for control of many of the network resources in the GENI backbone and at meso-scale campus locations.  Many experimenters can use these GENI resources without learning !OpenFlow.  The GENI [mailto:help@geni.net] can help arrange connectivity across your GENI slice, including IP connectivity and/or layer 2 VLANs.
    6 
    7 For experimenters who desire control over the network switching fabric in their slices, !OpenFlow provides increased flexibility.  Your experiment will incorporate an !OpenFlow controller.  If you have never written a controller, don't panic.  Many experiments can use existing controller code as-is, or with relatively simple modifications.  The GPO is available to help design your controller and plan your experiment configuration.  Feel free to contact us at [mailto:help@geni.net].
    8 
    9 The example captured in this page uses credentials from pgeni.gpolab.bbn.com, the GPO ProtoGENI Clearinghouse, to set up an experiment that includes 3 fictional sites (1 PG and 2 MyPLC nodes). This example assumes that an !OpenFlow Controller, such as NOX, is running on a slice resource, and is available and is accessible to the !FlowVisor instances. In this scenario, two sites are Web Servers and 3 are clients, as shown in the diagram below:
     5This page illustrates an !OpenFlow (OF) example for the [wiki:HowToUseOmni Omni How-to] page. [http://www.openflow.org/ OpenFlow] is used for the control of the network resources in the GENI backbone and at meso-scale campus locations.  Experimenters can use these GENI resources without learning !OpenFlow.  The GPO [mailto:help@geni.net] can help arrange connectivity across your GENI slice, including IP connectivity and/or layer 2 VLANs.
     6
     7For experimenters who desire control over the network switching fabric in their slices, !OpenFlow provides increased flexibility.  Your experiment will incorporate an !OpenFlow controller. Many experimenters use existing 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 [mailto:help@geni.net].
     8
     9The example captured in this page uses credentials from pgeni.gpolab.bbn.com, the GPO ProtoGENI Clearinghouse, to set up an experiment that includes 3 meso-scale OpenFlow sites (1 PG and 2 MyPLC nodes). This example shows a NOX !OpenFlow Controller running on a slice resource, and is available and is accessible to the FOAM instances. In this scenario, two sites are Web Servers and 3 are clients, as shown in the diagram below:
    1010
    1111[[Image(OF-Experiment-example.jpg)]]
    1212
    13 Omni tools can be used to reserve OF resources in each of the site's !OpenFlow Aggregate Manager (OF AM). Steps that are to take place include:
     13Omni tools are used to reserve resources in each of the site's !FlowVisor !OpenFlow Aggregate Manager (FOAM) and GENI Aggregate Managers. All steps required to set up both Compute and Network Resources are outlined in this page:
    1414    * Configure Omni tools
    15     * Define !OpenFlow RSPEC
    16     * Request flowspace resources
    17     * Opt-in Manager Administrative approval
     15    * Define !OpenFlow RSpecs for sites
     16    * Define !OpenFlow RSpecs for GENI Core.
     17    * Define Compute Resources RSpecs for MyPLC and PG sites.
     18    * Request flowspace resources for sites and core.
     19    * Request compute resources from sites
     20    * Confirm connection
    1821    * Run the experiment
    1922
    20 Note: Open Flow Aggregate Manager sites must be federated in order to trust a Clearinghouse. This is an OF administrator task that must take place before any of the user OF operations can take place.
     23Note: FOAM sites must be federated in order to trust a Clearinghouse. This is an OF administrator task that must take place before any of the user OF operations can take place.
    2124
    2225== Authentication and Omni tools configuration ==