Changes between Version 1 and Version 2 of GEC17Agenda/AdvancedOpenFlow/Procedure/DesignSetup


Ignore:
Timestamp:
07/19/13 22:17:09 (11 years ago)
Author:
nriga@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GEC17Agenda/AdvancedOpenFlow/Procedure/DesignSetup

    v1 v2  
    1717
    1818== 1.  Obtain resources ==
    19 For this experiment we are going to use resources in ExoGENI GPO or ExoGENI RENCI, we will need:
    20   * 6 VM (KVM): 2 (inside, outside) act as regular hosts; 2 (left, right) as regular switch; 2 (aggregator, switch) as OpenFlow Switch (we will only program one: switch)
     19For this experiment we are going to use ExoGENI resources, we will need:
     20  * 6 VM (KVM): 2 (inside, outside) act as regular hosts; 2 (left, right) as regular switches; 2 (aggregator, switch) as OpenFlow switches (we will only program one: switch)
    2121If you are attending a Tutorial, the resources might have already been reserved for you, check with your instructor and skip this step.
    2222
    … …  
    2727    - '''Switch:''' This node is a Linux host running Open vSwitch. Your Load Balancing OpenFlow Controller will be running on this node as well. '''This is the main node that you will be working on'''.
    2828    - '''Traffic Shaping Nodes (Left and Right)''': These are Linux hosts with two network interfaces. You can configure netem on the two traffic shaping nodes to have differing characteristics; the specific values don’t matter, as long as they are reasonable. Use several different delay/loss combinations as you test your load balancer.
    29     - '''Aggregator''': This node is a Linux host running Open vSwitch with a switch controller that will cause TCP connections to “follow” the decisions made by your OpenFlow controller on the Switch node. So leave this node alone, you only need to implement the OpenFlow controller on node "Switch".
     29    - '''Aggregator''': This node is a Linux host running Open vSwitch with a switch controller that will cause TCP connections to “follow” the decisions made by your OpenFlow controller on the Switch node. You will not need to change anything on this node, you only need to implement the OpenFlow controller on node "Switch".
    3030
    3131You can use any reservation tool you want to reserve this topology:
    32   * For Omni or Flack you can use the  [wiki:GENIExperimenter/RSpecs RSpec] that is published at: http://www.gpolab.bbn.com/experiment-support/OpenFlowExampleExperiment/ExoGENI/openflow-loadbalancer-kvm.rspec and the ExoGENI GPO AM or the ExoGENI RENCI AM
    33   * At the [https://portal.geni.net GENI Experimenter Portal] there is a public RSpec called "'''openflow-load-balancer-kvm'''" that you can use, and either '''GPO ExoGENI''' or '''RENCI ExoGENI''' as the AM
     32  * For Omni or Flack you can use the  [wiki:GENIExperimenter/RSpecs RSpec] that is published at: http://www.gpolab.bbn.com/experiment-support/OpenFlowExampleExperiment/ExoGENI/openflow-loadbalancer-kvm.rspec and any ExoGENI AM
     33  * At the [https://portal.geni.net GENI Experimenter Portal] there is a public RSpec called "'''openflow-load-balancer-kvm'''" that you can use, and either of the ExoGENI AMs
    3434
    35 Look at the [http://groups.geni.net/geni/wiki/GENIEducation/SampleAssignments/OpenFlowLoadBalancerTutorial/ExerciseLayout#Prerequisites Prerequisites] for Tutorials about reserving resources.
     35Look at the [wiki:GEC17Agenda/AdvancedOpenFlow/Procedure#Prerequisites Prerequisites] for Tutorials about reserving resources.
    3636
    3737= [wiki:GEC17Agenda/AdvancedOpenFlow/Procedure Introduction] =