Changes between Version 8 and Version 9 of CmuLab
- Timestamp:
- 02/03/09 16:24:16 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CmuLab
v8 v9 95 95 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. 96 96 97 '''System Status''' 98 '''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. 99 100 '''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. 101 102 '''Emulator nodes''': Are operational and managed by CMULab boss. 103 97 104 98 105 '''GPO Liason System Engineer'''