OpenFlow Demos at GEC8

July 21st, 2010, Guido Appenzeller in OpenFlow Blog

Today was the demo session at the GENI Engineering Conference in San Diego and the demos included a number of OpenFlow systems.

OpenFlow at GEC8

  • Integrated Control Framework Demo by a joint team of Stanford University and BBN. Using the OMNI command line tool, a researcher can reserve both PlanetLab compute nodes as well as an OpenFlow based networking substrate. The demo used the Expedient aggregate manager for OpenFlow Networks as well as the Opt-In manager. Essentially all of this demo came together over the past 4 weeks due to a heroic effort of the Stanford and BBN teams. Wiki page with more information is here.
  • Expedient, a control framework with a graphical UI for OpenFlow based resources. The version demonstrated additionally can be accessed via the GENI API through a proxy.
  • Aster*x, the OpenFlow based load balancer. This is the successor to the plug-n-serve system and the demo ran across a number of OpenFlow networks including Stanford, BBN, Princeton, Indiana and University of Washington.
  • Transport and Aggregation. This was a combination of the aggregation demo from SIGCOMM 2009 and the optical transport integration done together with Ciena. Details here.
  • WiMax. A demo from the OpenRoads team done together with two other WiMax demos at the conference.
  • Clemson University showed their graphical UI for configuring the slices on their local OpenFlow deployment. The UI looked great and there are a number of similarities with the Expedient UI.

Thanks to the 20+ people involved in putting these demos together, they were a big success. A few pictures below, more in the photo gallery of the demo session.

Tags: , , ,

One Response to “OpenFlow Demos at GEC8”

  1. Josh Says:

    Two other OpenFlow demos at GEC 8, which aren’t part of the OpenFlow Campus Trials project: http://groups.geni.net/geni/wiki/GEC8DemoSummary#GENIPathlets and http://groups.geni.net/geni/wiki/GEC8DemoSummary#OpenFlowatUniversityofWisconsin:PacketLevelRedundancyEliminationREonNetworkElements

Leave a Reply