Changes between Initial Version and Version 1 of CmuLab

12/03/08 16:33:38 (14 years ago)



  • CmuLab

    v1 v1  
     3<img src=""/>
     7'''Project Number'''
     11'''Project Title'''
     13Prototype Support for Heterogenous Testbed Resources:
     14Integrating cluster, broadband, and wireless emulation nodes into the “Proto-
     15GENI” Framework[[BR]]
     16a.k.a. CMU Testbeds, CMU Homenet (obsolete), CMULab, CMULAB
     18'''Technical Contacts'''
     20Principal Investigator: David Andersen[[BR]]
     21CoPI: Peter Steenkiste[[BR]]
     22CoPI: Srini Seshan[[BR]]
     23Lead Developer: Pat Gunn
     25'''Participating Organizations'''
     27Carnegie Mellon University, Pittsburgh, PA[[BR]]
     29Army Research Office[[BR]]
     30[ CMU Cylab]
     34This project will build upon CMU’s existing cluster, neighborhood wireless/broad-band, and wireless emulation testbeds to concretely identify—and build prototypes of—the authentication, resource arbitration, and node management primitives needed to coherently deal with this very diverse set of resources. The project will integrate these testbeds with the ProtoGENI effort from the University of Utah, which is itself based upon that group’s Emulab software.
     36The primary contributions of this work towards GENI Spiral 1 are the integration of HOMENET, CMU wireless emulator, and CMULab into the ProtoGENI control framework (includes federation & Internet2 connectivity); extension of HOMENET capabilities to support node/experiment management & isolation; definition/refinement of control framework elements such as RSpecs; and expansion of HOMENET user opt-in control.
     40milestone:"CMU Lab: Get CMU ProtoGENI node on I2 VLAN"
     42milestone:"CMU Lab: bare bones node configuration"
     44milestone:"CMU Lab: emulator nodes integrated"
     46milestone:"CMU Lab: Formulate initial RSpecs for wireless nodes"
     48milestone:"CMU Lab: deploy and operate 2 HomeNet nodes in CMU lab"
     50milestone:"CMU Lab: Tunneling packets from Utah to CMU"
     52milestone:"CMU Lab: desired node config & boot mgmt functionality"
     54milestone:"CMU Lab: Deploy and commence operations of 5 residential HomeNet nodes"
     56milestone:"CMU Lab: Emulator user interface integration"
     58milestone:"CMU Lab: IP-in-IP encap from CMU-Control to Homenet nodes"
     60milestone:"CMU Lab: integrate with ProtoGENI control plane"
     62milestone:"CMU Lab: integration of node-CMU and CMU-Utah tunnels"
     64milestone:"CMU Lab: Merge patches into ProtoGENI distribution"
     66milestone:"CMU Lab: student testbed use"
     68milestone:"CMU Lab: GEC Demo"
     70milestone:"CMU Lab: Integrated experimentation between CMU testbeds"
     72'''Project Technical Documents'''
     74  ''none at this time''
     76'''Spiral 1 Connectivity'''
     78  '''IP'''
     80    The CMU Lab internal cluster and Wireless Emulator are NATted behind  The Lab will connect to the nearest ProtoGENI node on Internet2 via GRE tunnel (unless an economical VLAN strategy can be found).  CMU access the Internet via 3ROX operated by PSC using a link with over 500 Mbps spare capacity.  3ROX is not on I2's DCN.
     82    !HomeNet nodes will tunnel (IP-in-IP) to CMU Control using OpenVPN.  The nodes will have addresses assigned by the user's ISP and may be assigned private addresses by !HomeNet.
     84  '''L2'''
     86    802.11q tagged VLANS will be used establish QoS-enabled Ethernet VLANs between the CMU emulab cluster and the CMU wireless emulator.  ProtoGENI will provide dynamic VLAN establishment between Utah emulab clusters and CMU Lab.
     88'''GPO Liason System Engineer'''
     90Aaron Falk
     92'''Related Projects'''
     94[ CMU EmuLab][[BR]]
     96[ Wireless Emulator]