Version 9 (modified by, 9 years ago)

adding bit about system status

Project Number


Project Title

Prototype Support for Heterogenous Testbed Resources: Integrating cluster, broadband, and wireless emulation nodes into the “Proto- GENI” Framework
a.k.a. CMU Testbeds, CMU Homenet (obsolete), CMULab, CMULAB

Technical Contacts

Principal Investigator: David Andersen
CoPI: Peter Steenkiste
CoPI: Srini Seshan
Lead Developer: Pat Gunn

Participating Organizations

Carnegie Mellon University, Pittsburgh, PA
Army Research Office
 CMU Cylab


This 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.

The 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.


milestone:"CMU Lab: Get CMU ProtoGENI node on I2 VLAN"
milestone:"CMU Lab: bare bones node configuration" (completed 12/1/08)
milestone:"CMU Lab: emulator nodes integrated" (completed 12/1/08)
milestone:"CMU Lab: Formulate initial RSpecs for wireless nodes"
milestone:"CMU Lab: deploy and operate 2 HomeNet nodes in CMU lab" (completed 1/31/09)
milestone:"CMU Lab: Tunneling packets from Utah to CMU"
milestone:"CMU Lab: desired node config & boot mgmt functionality" (completed 1/21/09)
milestone:"CMU Lab: Deploy and commence operations of 5 residential HomeNet nodes"
milestone:"CMU Lab: Emulator user interface integration"
milestone:"CMU Lab: IP-in-IP encap from CMU-Control to Homenet nodes"
milestone:"CMU Lab: integrate with ProtoGENI control plane"
milestone:"CMU Lab: integration of node-CMU and CMU-Utah tunnels"
milestone:"CMU Lab: Merge patches into ProtoGENI distribution"
milestone:"CMU Lab: student testbed use"
milestone:"CMU Lab: GEC Demo"
milestone:"CMU Lab: Integrated experimentation between CMU testbeds"

Project Technical Documents

none at this time

Quarterly Status Reports

4Q08 Status Report

Spiral 1 Connectivity


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 accesses the Internet via 3ROX operated by PSC using a link with over 500 Mbps spare capacity. 3ROX is not on I2's DCN.

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.


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.

Homenet Nodes

The Homenet nodes themselves are located in residences, sometimes behind NATs and sometimes with direct IP connectivity. To present a unified access mechanism for these nodes and to simplify the node management process, these nodes establish an SSL-based VLAN with the CMULab cluster control node (boss). The nodes use the open-source OpenVPN SSL/TLS-based VPN software to establish the Homenet control VPN.

System Status

CMULab cluster machines: Online and managed by CMULab boss. Available for experimental use by internal and external researchers. Nodes currently only have one Ethernet interface - are mostly viewed as eventual end-nodes and traffic-shaping nodes for wireless experimentation, and as virtual-node hosts for Emulab-style experimentation.

Homenet wide-area machines: Two nodes are operational sitting next to each other at CMU behind a NAT box installed here for testing purposes. First "real-world" node to be deployed 3 Feb 2009. Nodes boot from USB dongle, download disk images from the boss node over the Internet, install the image, transfer control, and boot up as a functioning testbed node. Nodes now perform all interaction with the testbed control using their public/private keypair as only identifier. As a result, testbed now supports nodes receiving dynamic addresses via DHCP and automatically updating database at CMULab with node-ID to dynamic IP address binding. Multiple nodes can be behind the same NAT/IP address and receive configurations appropriately.

Emulator nodes: Are operational and managed by CMULab boss.

GPO Liason System Engineer

Aaron Falk

Related Projects

 CMU EmuLab

 Wireless Emulator