Changes between Version 24 and Version 25 of GENIExperimenter/Tutorials


Ignore:
Timestamp:
08/26/16 10:43:24 (3 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/Tutorials

    v24 v25  
    1111|| Lab Zero: A First Experiment Using GENI [[BR]] Versions: [wiki:GENIExperimenter/Tutorials/jacks/GettingStarted_PartI/Procedure Jacks] or [wiki:GENIExperimenter/Tutorials/jFed/GettingStarted_PartI/Procedure jFed] Tools || [[Image(http://groups.geni.net/geni/raw-attachment/wiki/GENIExperimenter/Tutorials/Images/JacksScreen.png, nolink, 20%)]] [[Image(http://groups.geni.net/geni/raw-attachment/wiki/GENIExperimenter/Tutorials/Images/jFedScreen.png, nolink, 25%)]]|| This is a first, simple experiment on GENI useful for familiarizing new experimenters with GENI and the tools for using GENI. The high levels goals for this exercise are to: [[BR]] [[BR]]1. Do a simple but complete GENI experiment.[[BR]] 2. Learn and use 5 GENI terms: experimenter, project, slice, resource, and aggregate.[[BR]] 3. Use the [http://portal.geni.net GENI Experimenter Portal] and Jacks or jFed. ||
    1212
    13 || Lab One: Understanding the AM API using Named Data Networking] [[BR]] Versions: [wiki:GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure Jacks] or [wiki:GENIExperimenter/Tutorials/jFed/GettingStarted_PartII_ndn/Procedure jFed] Tools|| [[Image(http://groups.geni.net/geni/raw-attachment/wiki/GENIExperimenter/Tutorials/Graphics/topology.png, nolink, 70%)]] ||  This is a first, simple experiment on GENI useful for familiarizing new experimenters with GENI and the tools for using GENI. The high levels goals for this exercise are to: [[BR]] [[BR]]1. Understand what happens behind the scenes when you run and experiment in GENI [[BR]]2. Learn about RSpecs and the GENI AM API [[BR]]3.Learn about the Omni experimenter tool.[[BR]][[BR]] You will learn these concepts by running an experiment based on the  Named Data Networking (NDN) Future Internet Architecture. NDN software will be installed on the nodes in your network and you will run an application on top of the NDN software that fetches content by name. Optionally, you can instrument you application using the GENI Desktop to see graphs of traffic on the network links. This will give you greater insight into when application data is fetched from a cache and when it comes all the way from a data source.  ||
     13|| Lab One: Understanding the AM API using Named Data Networking [[BR]] Versions: [wiki:GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure Jacks] or [wiki:GENIExperimenter/Tutorials/jFed/GettingStarted_PartII_ndn/Procedure jFed] Tools|| [[Image(http://groups.geni.net/geni/raw-attachment/wiki/GENIExperimenter/Tutorials/Graphics/topology.png, nolink, 70%)]] ||  This is a first, simple experiment on GENI useful for familiarizing new experimenters with GENI and the tools for using GENI. The high levels goals for this exercise are to: [[BR]] [[BR]]1. Understand what happens behind the scenes when you run and experiment in GENI [[BR]]2. Learn about RSpecs and the GENI AM API [[BR]]3.Learn about the Omni experimenter tool.[[BR]][[BR]] You will learn these concepts by running an experiment based on the  Named Data Networking (NDN) Future Internet Architecture. NDN software will be installed on the nodes in your network and you will run an application on top of the NDN software that fetches content by name. Optionally, you can instrument you application using the GENI Desktop to see graphs of traffic on the network links. This will give you greater insight into when application data is fetched from a cache and when it comes all the way from a data source.  ||
    1414
    1515|| [wiki:GENIExperimenter/Tutorials/OpenFlowOVS Introduction to OpenFlow using POX] || [[Image(http://groups.geni.net/geni/raw-attachment/wiki/GENIExperimenter/Graphics/SimpleOpenFlow.jpg, nolink, 40%)]] ||  This is a simple OpenFlow tutorial that will guide you through the writing of simple OpenFlow controllers to showcase some of the OpenFlow capabilities.[[BR]] We are going to write three different controllers: [[BR]][[BR]] 1. A controller that will duplicate all the traffic of the OpenFlow switch out a specific port.[[BR]] 2. A TCP Port Forward controller will divert all traffic destined to host A on TCP port X to TCP port Y. [[BR]]3. And a Proxy Controller will divert all traffic destined to host A, TCP port X to host B, TCP port Y. [[BR]] [[BR]]In this tutorial we have a choice of using an OpenFlow Software Switch (Open vSwitch (OVS)) or using an OpenFlow-Capable Hardware Switch. ||