GENI-enabled Campuses Responsibilities, Requirements, & Coordination

1. GENI-enabled CampusesResponsibilities, Requirements, & Coordination Bryan Lyles, NSF Mark Berman &Chip Elliott, GPO / BBN

2. Recap • GENI is building out national-scale infrastructure of a radically new architecture • Sliced / virtualized • Deeply programmable • End-to-end • Fundamentally federated • GENI is one aspect of a larger, emerging picture of a major change in nationwide R&E infrastructure • New campus architectures - SDN, Science DMZ, . . . • Federated SDN-based, scientific cyber-infrastructure • Condo of Condos, XSEDE A major opportunity with very high potential impact for society

3. Responsibility of each participatingcampus in the nationwide effort • Identify campus contacts (research faculty and IT staff) who will actively collaborate on innovation, installation, and operations for GENI-enabling • Host a GENI rack • Deploy OpenFlow switches within campus • (At some campuses) Host a GENI WiMAX base station • Maintain OpenFlow- and VLAN-based connectivity to GENI via a research network • Make compute and network resources available to researchers on and off campus via aggregate manager API A nationwide federation – resources are locally owned,and shared with researchers on and off campus.

4. Roles & responsibilities(for discussion)

5. Next steps needed “Ramping up” “First wave” Trial operations add more campuses Revise /extend architectureas needed Initial deployments, Individual shakedowns, getting ready Equipment going live, end-to-end Winter / spring 2013 Summer 2013 onwards Late spring 2013 ?

6. Key challenges ahead • Document campus architecture(s) that support GENI / domain science based on hands-on experience and lessons learned in the early days • Thrash out best practices for end-to-end trouble-shooting in large-scale, federated infrastructure • Agree upon GENI governance structures as needed, including global / local policies and cost-recovery model(s)

7. How shall we organize ourselves? • Challenge #1 – Document campus architecture(s) that support GENI / domain science based on hands-on experience and lessons learned in the early days • Suggestions for volunteers . . . • Members of GENI architecture team • 2-3 “First wave” campus volunteers • 1 or more national / regional R&E networks • Active participation from CISE / OCI • GPO will help • Suggested logistics . . . • Regular phone calls, face to face meetings (at GECs?) • Wiki on geni.net

8. Organizing ourselves, cont’d • Challenge #2 – Thrash out best practices for end-to-end trouble-shooting in large-scale, federated infrastructure • Suggestions for volunteers . . . • GENI GMOC team (Indiana University) • 2-3 “First wave” campus volunteers • 1 or more national / regional R&E networks • GPO will help

9. Organizing ourselves, cont’d • Challenge #3 – Agree upon GENI governance structures as needed, including global / local policies and cost-recovery model(s) • Suggestions for volunteers . . . • Senior computer science researchers • 2-3 campus CIOs, whether first wave or later • 1 or more national / regional R&E networks • Active participation from CISE / OCI • GPO will help

10. Discussion • What are your thoughts on … • Other major challenges • Timeline / scheduling issues • Equipment / vendor issues • How we should organize ourselves • What key areas are being totally overlooked? • Are there areas in which additional near-term efforts could greatly reduce risk?

11. Thank you! • As a group, we are now poised at the start of something radically new . . . • . . . with potentially very high impact for the world • Of course there are many uncertainties –the map has not yet been drawn • Let’s go for it!