Changes between Version 1 and Version 2 of EnterpriseGENI/1Q09
- Timestamp:
- 06/29/09 15:17:14 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
EnterpriseGENI/1Q09
v1 v2 10 10 projects. 11 11 12 The OpenFlow Hypervisor (OFH) version 0.3 correctly performs network13 slicing of OpenFlow switches. We have successfully demonstrated12 The !OpenFlow Hypervisor (OFH) version 0.3 correctly performs network 13 slicing of !OpenFlow switches. We have successfully demonstrated 14 14 "multi-layer" network slicing, i.e., virtual network slices that 15 15 defined by any combination of physical layer (l1), link layer (l2), … … 23 23 available at http://www.openflowswitch.org/wk/index.php/GENILight. 24 24 25 We have rolled out an initial deployment of OpenFlow in one building at25 We have rolled out an initial deployment of !OpenFlow in one building at 26 26 Stanford. The plan is to use this deployment as a GENI substrate. We 27 27 currently run live traffic over the substrate to get experience with the … … 36 36 Manager. 37 37 38 The OpenFlow Hypervisor (OFH) virtualizes a physicalOpenFlow switch39 into multiple logical OpenFlow switches, which can be owned and38 The !OpenFlow Hypervisor (OFH) virtualizes a physical !OpenFlow switch 39 into multiple logical !OpenFlow switches, which can be owned and 40 40 operated by different experimenters. The OFH appears to a network of 41 OpenFlow switches as a single controller running as open-source42 software on a Linux-PC - the switches run the unmodified OpenFlow41 !OpenFlow switches as a single controller running as open-source 42 software on a Linux-PC - the switches run the unmodified !OpenFlow 43 43 Protocol (currently Version 0.8.9). The OFH is critical to allowing 44 44 multiple experimenters to run independent experiments simultaneously … … 46 46 (1) A policy engine that defines the logical switches (e.g. "all http 47 47 traffic", "Aaron's traffic", "Network administrator's experimental 48 traffic between 12midnight and 3am"), and (2) An OpenFlow mux/demux49 that implements the policy by directing OpenFlow commands to/from an50 OpenFlow controller and its network of logicalOpenFlow switches.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. 51 51 52 52 Current implementation status: Version 0.3 of the OFH has successfully … … 56 56 nodes in Stanford, Internet2 (Houston, New York, Los Angelas), and 57 57 JGNPlus (Japan). Version 0.3 of the OFH has also been used to slice 58 wireless networks in a project called OpenRoads, where each mobile58 wireless networks in a project called !OpenRoads, where each mobile 59 59 node has their own slice with their own corresponding mobility 60 60 manager. Plans are underway to incorporate the OFH (now renamed 61 " FlowVisor") into the productionOpenFlow deployment in the Gates61 "!FlowVisor") into the production !OpenFlow deployment in the Gates 62 62 building. 63 63 64 64 The Aggregate Manager will build on top of the OFH -- essentially, the 65 Aggregate Manager is an OpenFlow controller that controls a subset of65 Aggregate Manager is an !OpenFlow controller that controls a subset of 66 66 the network resources, as defined by the local administrator. We are 67 67 currently drafting the aggregate manager architecture and integrating 68 it with the HyperVisor. We proposed an API between the Aggregate68 it with the !HyperVisor. We proposed an API between the Aggregate 69 69 Manager and clearing house, as mentioned above. 70 70 … … 80 80 Publications (individual and organizational) 81 81 82 No publications as of yet, but work involving the OpenFlow hypervisor83 is under submission to both Sigcomm 2009 and MobiComm.82 No publications as of yet, but work involving the !OpenFlow hypervisor 83 is under submission to both Sigcomm 2009 and !MobiComm. 84 84 85 85 Collaborations