Chip Elliott GENI Project Director June 22, 2010 geni

1. GENIOpenFlow as aNetworking SubstrateOpenFlow / Software Defined NetworksCIO Summit, Stanford – June 22, 2010 Chip Elliott GENI Project DirectorJune 22, 2010 www.geni.net

2. Outline • GENI – Exploring future internets at scale • GENI’s OpenFlow status and plans • GENI Spiral 2 • Meso-scale buildout • Starting experimentation • Looking ahead

3. Global networks are creatingextremely important new challenges Credit: MONET Group at UIUC Science Issues We cannot currently understand or predict the behavior of complex,large-scale networks Innovation Issues Substantial barriers toat-scale experimentation with new architectures, services, and technologies Society Issues We increasingly rely on the Internet but are unsure we can trust its security, privacy or resilience

4. GENI Conceptual DesignInfrastructure to support at-scale experimentation Sensor Network Federated International Infrastructure Edge Site Mobile Wireless Network GENI-enabled at-scaleinfrastructure Virtualized Deeply programmable Programmable & federated, with end-to-end virtualized “slices” GENI-enabled at-scaleinfrastructure Heterogeneous, and evolving over time via spiral development

5. How We’ll Use GENI Note that this is the “classics illustrated” version – a comic book!Please read the Network Science and Engineering Research Agenda to learn all about the community’s vision for the research it will enable. Your suggestions are very much appreciated!

6. A bright idea I have a great idea! The original Internet architecture was designed to connect one computer to another – but a better architecture would be fundamentally based on PEOPLE and CONTENT! That will never work! It won’t scale! What about security? It’s impossible to implement or operate! Show me!

7. Trying it out My new architecture worked great in the lab, so now I’m going to try a larger experiment for a few months. And so he poured his experimental software into clusters of CPUs and disks, bulk data transfer devices (‘routers’), and wireless access devices throughout the GENI suite, and started taking measurements . . . He uses a modest slice of GENI, sharing its infrastructure with many other concurrent experiments.

8. It turns into a really good idea Boy did I learn a lot! I’ve published papers, the architecture has evolved in major ways, and I’m even attracting real users! Location-based social networks are really cool! His experiment grew larger and continued to evolve as more and more real users opted in . . . His slice of GENI keeps growing, but GENI is still running many other concurrent experiments.

9. Experiment turns into reality My experiment was a real success, and my architecture turned out to be mostly compatible with today’s Internet after all – so I’m taking it off GENI and spinning it out as a real company. I always said it was a good idea, but way too conservative.

10. Meanwhile . . . I have a great idea! If the Internet were augmented with a scalable control plane and realtime measurement tools, it could be 100x as reliable as it is today . . . ! And I have a great concept for incorporating live sensor feeds into our daily lives ! If you have a great idea, check out theNSF CISE Network Scienceand Engineering program.

11. Outline • GENI – Exploring future internets at scale • GENI’s OpenFlow status and plans • GENI Spiral 2 • Meso-scale buildout • Starting experimentation • Looking ahead

12. Spiral DevelopmentGENI grows through a well-structured, adaptive process • GENI Spiral 2Early experiments, meso-scale build, interoperable control frameworks, ongoing integration, system designs for security and instrumentation, definition of identity management plans. • Envisioned ultimate goalExample: Planning Group’s desired GENI suite, probably trimmed some ways and expanded others. Incorporates large-scale distributed computing resources, high-speed backbone nodes, nationwide optical networks, wireless & sensor nets, etc. • Spiral Development ProcessRe-evaluate goals and technologies yearly by a systematic process, decide what to prototype and build next. Planning Design Use Use Integration Build out GENI Prototyping Plan

13. Current GENI StatusGENI-enabling testbeds, campuses, and backbones

14. CNRI

15. Building the GENI Meso-scale PrototypeCurrent plans for locations & equipment OpenFlow WiMAX Stanford U Washington Wisconsin Indiana Rutgers Princeton Clemson Georgia Tech Stanford UCLA UC Boulder Wisconsin Rutgers Polytech UMass Columbia OpenFlow Backbones ShadowNet Seattle Salt Lake City Sunnyvale Denver Kansas City Houston Chicago DC Atlanta Salt Lake City Kansas City DC Atlanta Juniper MX240 Ethernet Services Router NEC WiMAX Base Station Arista 7124S Switch NEC IP8800 Ethernet Switch HP ProCurve 5400 Switch

16. OpenFlow Deployment Roadmap

17. GENI Interoperability • Currently four GENI control-framework “clusters” • PlanetLab, ProtoGENI, ORBIT, ORCA • This summer’s goal: interoperability • PlanetLab, ProtoGENI just became interoperable • Software checked into main trunk of both projects • ORCA interoperability expected within weeks • OpenFlow interoperability expected soon • Open mix-and-match of tools / technologies

18. Building the experiment pipeline • Three pipeline efforts to encourage experiments • Getting earliest experiments running (now) • Organizing / running training sessions (GEC 7, 8, . . .) • NSF-sponsored experimentation workshop (June) • NSF Future Internet Architectures program

19. GENI Experimenters WorkshopPrinceton, June 29-30, 2010 • Aster*x: Load-Balancing Web Traffic over Wide-Area Networks (Nikhil Handigol, Stanford, and Srini Seetharaman, Deutsche Telekom R&D Lab) • Federated GENI Prototypes for Supporting Distributed Software Development (Pierre F. Tiako and Paoli Wognakou, Langston University) • Performance Evaluation of Intra-domain Bandwidth Allocation and Inter-Domain Routing Algorithms (Kaiqi Xiong and Ranadheer Pendru, Texas A&M) • Experiments with the Phoebus Session Layer and a Monitoring Framework (Martin Swany and Ezra Kissel, U. Delaware) • Migrating Enterprises to Cloud-based Architectures (Sanjay Rao and Mohammed Hajjat, Purdue) • Programmable Packet Networks over Dynamic Circuit Substrate (Jeff Chase and Xin Liu, Duke) • GridStat GENI Experiment (Carl Hauser and Shariful Shaikotm, Washington State) • Network-Wide Policies With OpenFlow (Joon Kim and Sam Burnett, GA Tech) • Scaling the Network Infrastructure using OpenFlow in the Wide Area Network (Chris Small, Indiana University) • Generating Realistic Synthetic TCP Application Workloads (Kevin Jeffay and Jay Aikat, U. North Carolina) • Massive-Scale Experimentation of Location Based Video Streaming on Content Distribution Networks (Jason Liu, Florida International University, and Tim Ficarra, University of Massachusetts--Lowell) • Multilayer Network Resilience Analysis and Experimentation (James Sterbenz and Justin Rohrer, Kansas University) • Ethical and Political Values Embedded in Networks and Information System Design (Finn Brunton and Helen Nissenbaum, New York University) • Chairs • Jen Rexford, Princeton • Guru Parulkar, Stanford • Participants • CloudNet (Aaron Gember and Theo Benson, U. Wisconsin--Madison) • Socially Aware Single-System Image (Chunming Qiao and Lokesh Mandvekar, U. Buffalo) • MeasuRouting: Routing-Assisted Traffic Monitoring (Chen-Nee Chuah and Guanyao Huang, UC Davis) • Secure Information Retrieval/Exchange in Extreme Networks (Mooi Choo Chuah and Charles Gerlach, Lehigh University) • Deconstructing Fine-scale Probing in Ultra-high Speed and Virtualized Networks (Jasleen Kaur and Eric Gavaletz, U. North Carolina) • Pathlet Routing and Adaptive Multipath Algorithms (Brighten Godfrey and Ashish Vulimiri, UIUC) • Pervasive Data Sharing over Heterogeneous Networks (Helen Wang and Lianyu Zhao, Clemson) • Network Security and Traffic Analysis (Richard Brooks and Yu Lu, Clemson) • Core and Edge Network Optimization for Mobile Gigabit Wireless Access (KC Wang, Clemson, and Chin-Ya Huang, U. Wisconsin--Madison) • Evaluating Congestion Control Protocols for Next Generation Networks (Ihsan Ayyub Qazi and Rami Melhem, U. Pittsburgh) • In-network Storage and Computation (Z. Morley Mao and Yudong Gao, U. Michgan) • Storage Aware Routing Protocol under a Full Range of Generalized DTN Scenarios (Shweta Jain and Akash Baid, Rutgers) • Mobility and Delay Tolerant Content Delivery in Software-Defined Programmable Wireless Access Network (Kok-Kiong Yap and Sachin Katti, Stanford)

20. Outline • GENI – Exploring future internets at scale • GENI’s OpenFlow status and plans • GENI Spiral 2 • Meso-scale buildout • Starting experimentation • Looking ahead

21. GENI Solicitation 3 • Solicitation areas • Aggressively grow meso-scale build (next slide) • Enhanced regional & backbone buildouts • More WiMAX sites • New “GENI Racks” (eg rack of PCs with OpenFlow switch) • GENI Instrumentation system (build & deploy) • Experiment support / training / education & curriculum development • Solicitation document: see www.geni.net • Proposal deadline: August 20, 2010

22. These are exciting timesall around the world! ETRI G-LAB FIRE JGN2plus + Akari China Brazil NICTA The GENI project is actively collaborating with peer efforts outside the US, based on equality and arising from direct, “researcher to researcher” collaborations.

23. GENI Engineering ConferencesMeet every 4 months to review progress together 8th meeting, open to all:July 20 – 22, 2010, San Diego, CA Team meetings, integrated demos, Working Group meetings Also discuss GPO solicitation, how to submit a proposal, evaluation process & criteria, how much money, etc. Travel grants to US academics for participant diversity Subsequent Meetings, open to all who fit in the room Held at regular 4-month periods Held on / near university campuses (volunteers?) All GPO-funded teams required to participate Systematic, open review of each Working Group status(all documents and prototypes / trials / etc.) Also time for Working Groups to meet face-to-face Discussion will provide input to subsequent spiral goals