| | 1 | = CMU Lab Quarterly Status Report 1Q 2010, ending March 2010 = |
| | 2 | |
| | 3 | == Major accomplishments == |
| | 4 | === A. Milestones Achieved === |
| | 5 | * Design complete for Cisco VLAN-based data plane integration over disparate testbeds (#215) |
| | 6 | The broad design for using single interfaces and 802.1Q to seperate control |
| | 7 | and data plane traffic was completed. |
| | 8 | * Software to automate OpenVPN configuration, server management, and configuration |
| | 9 | bookkeeping (#301) |
| | 10 | MetaVPN, which replaces the manual work done in our past configuration and |
| | 11 | use of OpenVPN, was completed. This makes management of nodes in a VPN as well |
| | 12 | as creation or destruction of VPNs simple, quick, and scriptable. |
| | 13 | * Event system work done allowing for more automation/integration of Wireless emulation |
| | 14 | by using the Emulab event system to control automated emulator tasks. This work |
| | 15 | is more general and benefits the entire Emulab community. |
| | 16 | === B. Deliverables made === |
| | 17 | * MetaVPN |
| | 18 | MetaVPN is usable either in the context of a network testbed or in a standalone |
| | 19 | mode, allowing for easy and scriptable management of OpenVPN instances. The |
| | 20 | software is documented and was presented at a GEC. |
| | 21 | * Event system work |
| | 22 | Patches were submitted and accepted at Utah that allow for a new category of |
| | 23 | events that happen as an experiment is swapped out. |
| | 24 | |
| | 25 | == II. Description of work performed during the last quarter == |
| | 26 | === A. Activities and findings === |
| | 27 | === C. Publications (individual and organizational) === |
| | 28 | None this quarter |
| | 29 | === D. Outreach activities === |
| | 30 | === E. Collaborations === |
| | 31 | As documented in the Utah quarterly report, we have been |
| | 32 | participating in weekly/biweekly conference calls |
| | 33 | with other members of our cluster. Our lead staff developer, |
| | 34 | Pat Gunn, has had other communications with smaller parts of |
| | 35 | the Emulab team as part of code design and development. |
| | 36 | |
| | 37 | === F. Other contributions === |
| | 38 | |
