ProtoGENI and PGAugmentation Spiral 2 Year-end Project Review

1. ProtoGENI and PGAugmentationSpiral 2 Year-end Project Review University of Utah, Internet2, HP Labs PI: John Regehr, Co-PI: Robert Ricci PIs at other Institutions: Matt Zekauskas, Rick McGeer Utah Staff: Leigh Stoller, Jon Duerig, Gary Wong, David Johnson, Dan ReadingUtah Students: SrikanthChikkulapelly, TarunPrabhu, Matt Strum Aug 25, 2010

2. Project Summary: ProtoGENI • This project includes a large-scale integration of existing and under-construction systems that provide key GENI functionality. The integration consists of four key components: • A nationwide, high-speed backbone on Internet2’s wave infrastructure • A set of sliceable, user programmable components embedded in this backbone, including PCs and “programmable hardware” NetFPGA cards • A set of subnets, including a variety of wireless networks, residential broadband, and programmable edge clusters, that will be connected to this backbone • Software from the University of Utah, based on an enhanced version of the Emulab testbed management software to manage the backbone, many of the subnets, and to provide a common point of integration between them. Aug 25, 2010

3. Project Summary: PGAugmentation This effort will integrate additional projects with the ProtoGENI control framework (Cluster C). It will provide new Cluster C projects with the software, standards, and technical assistance required to integrate their projects into the ProtoGENI control framework, and to refine the design of ProtoGENI to make smooth integration possible. These projects span a wide range of the GENI ecosystem, including international collaboration, instrumentation and measurement, hybrid environments involving multiple network technologies, early experiments, and aggregate deployments of sliceable networks, routers, storage, and hosts. Aug 25, 2010

4. Milestone & QSR Status: ProtoGENI Aug 25, 2010

5. Milestone & QSR Status: PGAugmentation Aug 25, 2010

6. Accomplishments 1: Advancing GENI Spiral 2 Goals • Continuous Experimentation • Worked directly with several early experimenters, and supported GENI Alpha effort • Gave tutorials at GEC8 and GENI Experimenters Workshop • Have added features based on user feedback (eg. disk loading) • 81 users created 1,789 slices since Jan. 1, 2010 • Mailing lists: geni-users: 487 messages, geni-dev: 774 messages (since Jan 1) • Integration • Ref. CM has been a bigger success than we expected: almost a dozen have been brought up • Several projects in Cluster C have demonstrated remarkable integration milestones • Bi-weekly cluster conference calls, much time spent on phone and email with cluster members • Instrumentation & Measurement • Have worked to get the many I&M projects in cluster C to collaborate • Made switch counters available to LAMP and GMOC • Interoperability • Made backbone resources available to some Cluster B members (SPP, GpENI, MAX) • Contributed to design of GENI AM API, enabled in ProtoGENI code now • Contributed to “SFA 2.0” • Security • Participated in GMOC emergency shutdown exercise Aug. 25, 2010

7. Accomplishments 2:Other Project Accomplishments • Current federation includes 21 CMs/SAs • 8 are consistently up and stable • 7 are up intermittently – generally ones that are in early development • 6 are consistently down, disabled in clearinghouse • International collaborations • Have been in contact with international groups interested in joining GENI: KISTI, TWISC • Hosting visiting scholar from KISTI, WoojinSeok, who is interested in GENI • Matt Strum gave a talk about ProtoGENI at KISTI • Participated in GENI/FIRE federation workshop • Outreach to national and regional networks • Organizing committee, QUILT (regional network) workshop • GENI talk at Internet2 fall member meeting 2009 • GENI talk at WestNet meeting, winter 2010 • Moved Internet2 links from wave to MPLS • Moved to a decentralized source code repository • Makes it much easier for sites to maintain their own local branches • Co-chair, CFWG • Hosted GEC6 Aug 25, 2010

8. Issues • Synchronized deadlines are hard on everybody, but especially the CFs • Everybody needs everything all at the same time… • GECs and demos are primary causes of this • Bright spot: relatively frequent milestones means end of spiral is not one of these times • GECs • Very frequent, and not all time spend on preparing, traveling, recovering furthers GENI goals • Consider moving to 2 per year? • Consider expanding role of tutorials and mini-workshops at GECs? • Contracting was a huge time sink last year • Our Solicitation 2 contracts were signed 4/9/2010, just 4 1/2 months ago • Uncertainty WRT national networks slows node deployment in POPs Aug. 25, 2010

9. Plans • Remainder of Spiral 2 • This week: Finish service implementer’s guide (PGAugmentation) • By end of month: Finish specification, order I2 POP hardware (ProtoGENI) • Ultimate goal is to get deployed by GEC9 (PGAugmentation) • By end of next month: Updated version of reference CM with GENI AM API (PGAugmentation) • Spiral 3 thoughts • Might want to re-evaluate PGAugmentation milestones – focus less on refreshes of APIs on a set schedule, and more on some interoperability tools (like RSpec translations) • Users, rather than developers, are going to get more important, requiring different kind of support • Will have to figure out plans for POP equipment hosting after Solicitation 1 funding ends Aug. 25, 2010