Changes between Version 1 and Version 2 of EnterpriseGENI/1Q09


Ignore:
Timestamp:
06/29/09 15:17:14 (10 years ago)
Author:
hdempsey@bbn.com
Comment:

Fix OpenFlow to not be wiki links

Legend:

Unmodified
Added
Removed
Modified
  • EnterpriseGENI/1Q09

    v1 v2  
    1010projects.
    1111
    12 The OpenFlow Hypervisor (OFH) version 0.3 correctly performs network
    13 slicing of OpenFlow switches.  We have successfully demonstrated
     12The !OpenFlow Hypervisor (OFH) version 0.3 correctly performs network
     13slicing of !OpenFlow switches.  We have successfully demonstrated
    1414"multi-layer" network slicing, i.e., virtual network slices that
    1515defined by any combination of physical layer (l1), link layer (l2),
     
    2323available at http://www.openflowswitch.org/wk/index.php/GENILight.
    2424
    25 We have rolled out an initial deployment of OpenFlow in one building at
     25We have rolled out an initial deployment of !OpenFlow in one building at
    2626Stanford. The plan is to use this deployment as a GENI substrate. We
    2727currently run live traffic over the substrate to get experience with the
     
    3636Manager.
    3737
    38 The OpenFlow Hypervisor (OFH) virtualizes a physical OpenFlow switch
    39 into multiple logical OpenFlow switches, which can be owned and
     38The !OpenFlow Hypervisor (OFH) virtualizes a physical !OpenFlow switch
     39into multiple logical !OpenFlow switches, which can be owned and
    4040operated by different experimenters. The OFH appears to a network of
    41 OpenFlow switches as a single controller running as open-source
    42 software on a Linux-PC - the switches run the unmodified OpenFlow
     41!OpenFlow switches as a single controller running as open-source
     42software on a Linux-PC - the switches run the unmodified !OpenFlow
    4343Protocol (currently Version 0.8.9). The OFH is critical  to allowing
    4444multiple experimenters to run independent experiments simultaneously
     
    4646(1) A policy engine that defines the logical switches (e.g. "all http
    4747traffic", "Aaron's traffic", "Network administrator's experimental
    48 traffic between 12midnight and 3am"), and (2) An OpenFlow mux/demux
    49 that implements the policy by directing OpenFlow commands to/from an
    50 OpenFlow controller and its network of logical OpenFlow switches.
     48traffic between 12midnight and 3am"), and (2) An !OpenFlow mux/demux
     49that implements the policy by directing !OpenFlow commands to/from an
     50!OpenFlow controller and its network of logical !OpenFlow switches.
    5151
    5252Current implementation status: Version 0.3 of the OFH has successfully
     
    5656nodes in Stanford, Internet2 (Houston, New York, Los Angelas), and
    5757JGNPlus (Japan).  Version 0.3 of the OFH has also been used to slice
    58 wireless networks in a project called OpenRoads, where each mobile
     58wireless networks in a project called !OpenRoads, where each mobile
    5959node has their own slice with their own corresponding mobility
    6060manager.  Plans are underway to incorporate the OFH (now renamed
    61 "FlowVisor") into the production OpenFlow deployment in the Gates
     61"!FlowVisor") into the production !OpenFlow deployment in the Gates
    6262building.
    6363
    6464The Aggregate Manager will build on top of the OFH -- essentially, the
    65 Aggregate Manager is an OpenFlow controller that controls a subset of
     65Aggregate Manager is an !OpenFlow controller that controls a subset of
    6666the network resources, as defined by the local administrator.  We are
    6767currently drafting the aggregate manager architecture and integrating
    68 it with the HyperVisor.  We proposed an API between the Aggregate
     68it with the !HyperVisor.  We proposed an API between the Aggregate
    6969Manager and clearing house, as mentioned above.
    7070
     
    8080Publications (individual and organizational)
    8181
    82 No publications as of yet, but work involving the OpenFlow hypervisor
    83 is under submission to both Sigcomm 2009 and MobiComm.
     82No publications as of yet, but work involving the !OpenFlow hypervisor
     83is under submission to both Sigcomm 2009 and !MobiComm.
    8484
    8585Collaborations