GENI Exploring Networks of the Future Niky Riga, GENI Project Office (nriga@bbn.com)

1. GENIExploring Networks of the FutureNiky Riga, GENI Project Office(nriga@bbn.com) www.geni.net

2. Outline • GENI – Exploring future internets at scale • The GENI Concept • Building GENI • Experimental and Classroom use of GENI • GENI: An experimenter’s view

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: Infrastructure for Experimentation GENI provides compute resources that can be connected in experimenter specified Layer 2 topologies.

5. GENI: Infrastructure for Experimentation GENI provides compute resources that can be connected in experimenter specified Layer 2 topologies.

6. Multiple GENI Experiments run Concurrently Resources can be shared between slices Experiments live in isolated “slices”

7. GENI is “Deeply Programmable” I install software I want throughout my network slice (into routers, switches, …) or control switches using OpenFlow Experimenters can set up custom topologies, protocols and switching of flows

8. GENI Compute Resources GENI Wireless compute nodes GENI Racks Existing Testbeds (e.g. Emulab)

9. GENI Networking Resources National Research Backbones (e.g. Internet2) Networking within a Rack Regional Networks (e.g. CENIC) WiMAX Base Stations

10. Outline • GENI – Exploring future internets at scale • The GENI Concept • Building GENI • Experimental and Classroom use of GENI • GENI: An experimenter’s view

11. A bright idea “I have a great idea.” “That will never work.”

12. Let’s try it out! My new architecture worked great in the lab, so now I’m going to try a larger experiment for a few months. He uses a modest slice of GENI, sharing its infrastructure with many other concurrent experiments.

13. It turns into a really good idea This service looks very useful His slice of GENI keeps growing, but GENI is still running many other concurrent experiments.

14. Attracts real users “Looks like an app to me.” “It’s my very own GENI slice.”

15. “Boy did I learn a lot!” “What a cool service.” (I wonder how it works.) “I always said it was a great idea.” (But way too conservative.)

16. ??

17. Moral of this story GENI is meant to enable . . . At-scale experiments Internet-incompatible experiments Both repeatable and “in the wild” experiments ‘Opt in’ for real users Instrumentation and measurement tools GENI creates a huge opportunity for ambitious research!

18. Outline • GENI – Exploring future internets at scale • The GENI Concept • Building GENI • Experimental and Classroom use of GENI • GENI: An experimenter’s view

19. Growing GENI’s footprint

20. FederationGENI grows by GENI-enabling heterogeneous infrastructure My experiment runs acrossthe evolving GENI federation. GENI Rack Commercial Clouds Backbone #1 Campus My GENI Slice Corporate GENI suites Access#1 Regional Research Testbed Non-US Testbeds This approach looks remarkably familiar . . . GENI Rack Avoidtechnology “lock in” and grow quickly by incorporating existing infrastructure

21. Infeasible to build a testbed as big as the Internet Build GENI at sufficient scale HP ProCurve 5400 Switch NEC WiMAX Base Station GENI-enabled equipment GENI-enabled campuses, students as early adopters “At scale” GENI prototype • GENI-enable testbeds, commercial equipment, campuses, regional and backbone networks Campus photo by Vonbloompasha

22. GENI architecture ISP Internet • Flexible network / cloud research infrastructure • Also suitable for physics, genomics, other domain science • Support “hybrid circuit” model plus much more (OpenFlow) • Distributed cloud (racks) for content caching, acceleration, etc. Metro Research Backbones g Layer 2 Data Plane GENI-enabled hardware g Legend Layer 3 Control Plane g Campus Regional Networks

23. Georgia Tech: a great example • OpenFlow in 4 GT lab buildings now • Aware Home • Students will “live in the future” – Internet in one slice, multiple future internets in additional slices Nick FeamsterPI Ellen Zegura Russ Clark, GT-RNOC Ron Hutchins, OIT Trials of “GENI-enabled” commercial equipment Toroki LightSwitch 4810 HP ProCurve 5400 Switch Juniper MX240 Ethernet Services Router HTC Android smart phone NEC WiMAX Base Station GENI racks Arista 7124S Switch NEC IP8800 Ethernet Switch

24. Example regional networkCENIC OpenFlow buildout

25. GENI on Internet2 A major step towards campus expansion • Collaboration to implement national-scale infrastructure • sliced and deeply-programmable • incorporating OpenFlow/SDN switches, GENI Racks,etc. • high-speed (10-100 Gbps) • With software that supports shared use by faculty, students, and campus IT organizations • In-progress migration from “prototype GENI” to AL2S production system • Scaling to an envisioned goal of 100-200 GENI campuses • ION AM to support dynamic provisioning within Internet2

26. GENI WiMAX Agreements • Agreement with Clearwire • Clearwire and Rutgers University have signed a master agreement • encompassing all WiMAX sites, to ensure operation in the EBS Band. • An emergency stop procedure, in case of interference with Clearwire service, has been agreed upon. • GENI Mobile Virtual Network Operator (MVNO) - Partner with Sprint and Arterra (a Sprint partner) to create and operate an (MVNO) that serves the academic research community - The effort is led by Jim Martin, Clemson Univ, and is underway with a 1 year NSF EAGER

27. Current GENI buildout • More WiMAX base stationswith Android handsets • GENI-enable 5-6regional networks • Inject moreOpenFlow switchesinto Internet2 • Add GENI Racks to 50 locationswithin campuses, regionals, andbackbone networks GENI Racks serve as programmable routers, distributed clouds, content distribution nodes, caching or transcoding nodes, etc

28. Creating and deploying GENI racks Ilia Baldine RENCI More resources / rack,fewer racks Rick McGeerHP Labs Fewer resources / rack,more racks ExoGENI Rack Installed at GPO – Feb 22, 2012

29. GENI WiMAX 2013 On the Air Not On the Air • 26 Wimax Base Stations in 13 Sites • Sliced, virtualized • and interconnected • Researcher-owned, • researcher-operated • 4G cellular systems

30. Federation Extends the Reach of GENI and International Peer Testbeds Initial plan to federate testbeds on five continents

31. Testbeds Involved Modified slide from:http://groups.geni.net/geni/attachment/wiki/GEC18Agenda/MonPlenary/GEC18_brecht_vermeulen_International_Federation.pdf

32. GENI Operations GMOC: GENI Meta-operation Center • Keeps track of outages • Notification system for resource reservation • Monitors most GENI Aggregates GMOC Google Calendar keeps track of reservations/outages

33. GMOC Calendar Scheduled Unscheduled

34. Current GMOC Operational Support • Monitor and triage problem resolution on the GENI Integrate OpenFlowCore network (Mesoscale) • Emergency Stop • GENI Experimenter Support • Manage network/systems alarms, outages, maintenances, • Mesoscale provisioning, maintenance freezes, demo reservations and disruptive experiment reservations (and post-mortem) • Notifications, Escalation and Reporting • Engineering configuration (Internet2, MOXI, Indiana) and new Aggregate site, regional and GENI rack turn-up • GMOC Measurement API for GENI Aggregates • Develop new tools for network monitoring and measurement Modified slide from:http://groups.geni.net/geni/attachment/wiki/GEC18Agenda/RackOpsAndMeasurement/GEC18%20GMOC%20Presentation.pdf

35. GENI Monitoring System • “Complete” monitoring system functionality motivated by three representative use cases: • LLR inquiry (Legal, Law Enforcement & Regulatory) • Usage and health report • Problem alerting and status • Components of system needed to support use cases: • Overview of components • Current status (what’s complete, what’s not started, what’s in progress) More on GENI Operations http://groups.geni.net/geni/wiki/GEC18Agenda/RackOpsAndMeasurement

36. Outline • GENI – Exploring future internets at scale • The GENI Concept • Building GENI • Experimental and Classroom use of GENI • GENI: An experimenter’s view

37. How is GENI being Used? Research • Future Internet architectures • Software defined networking • Large scale evaluation of smart grid protocols Education • Networking and Distributed systems classes • Cloud computing classes • WiMAX classes As of October 2013, GENI had over a 1200 users!

38. Three FIA Teams have Slices on GENI NDN (demo at GEC 13) XIA (demo at GEC15) MobilityFirst (demo at GEC 12 & GEC18) GENI is the only testbed that can support these teams.

39. Weather NowCastingUniversity of Massachusetts ViSE views steerable radars as shared, virtualized resources http://geni.cs.umass.edu/vise David Irwin et al Generate “raw” live data ViSE/CASA radar nodes http://stb.ece.uprm.edu/current.jsp Create and run realtime“weather service on demand”as storms turn life-threatening “raw” live data Nowcast images for display • Spin up system in Amazon commercial EC2 and S3 services on demand Multi-radar NetCDF Data Nowcast Processing

40. Virtual Desktop Cloud Prasad Calyam University of Missouri Program realtime load-balancing functionality deep into the network to improve QoE

41. GENI in the Classroom • Undergrad Classes • Reinforce learning of key concepts • Graduate classes • Hands-on experience of advanced concepts • Project in GENI • Classes in: • Computer Networking, Wireless and Mobile Networking, Distributed Systems, Cloud Computing 10-20 classes per semester

42. GENI at Upcoming Conferences

43. Outline • GENI – Exploring future internets at scale • The GENI Concept • Building GENI • Experimental and Classroom use of GENI • GENI: An experimenter’s view

44. Access to GENI Leverage InCommonfor single sign-on authentication Experimenters from 304 educational and research institutions have InCommon accounts • For many experimenters: • no new passwords • familiar login screens GENI Project Office runs a federated IdP to provide accounts for non-federated organizations.

45. The GENI Portal is… A web-based tool for experimenters to manage experimenters, projects, and slices.

46. For GENI IdP Accounts … • Sign up with an institutional email address (ientua.gr email) that you have access to • Forwarding on that email address is ok • Reply to follow up email confirming that you made the request • The account creation process can take a couple of days.

47. GENI: Terms and Definitions Slice Abstraction for a collection of resources capable of running experiments • An experiment uses resources in a slice • Slices isolate experiments • Experimenters are responsible for their slices

48. GENI: Terms and Definitions • Slice authority: Creates and registers slices • GENI slice authorities: PlanetLab, ProtoGENI, GPO Lab • Aggregate: Provides resources to GENI experimenters • Typically owned and managed by an organization • Examples: PlanetLab, Emulab, GENI Rack on various campuses • Aggregates implement the GENI AM API Slice Authority Create & Register Slice Slice credentials Aggregate Manager API - listResources - createSliver … Researcher Aggregate Manager Aggregate Resources

49. GENI: Terms and Definitions • Sliver: One or more resources provided by an aggregate • E.g. Bare machines, virtual machines, VLANs Campus#3 Commercial Clouds My slice contains slivers from many aggregates. Backbone #1 Campus My GENI Slice Corporate GENI suites Access#1 Backbone #2 Research Testbed Other-Nation Projects Campus#2

50. RSpecs • RSpecs: Lingua franca for describing and requesting resources • “Machine language” for negotiating resources between experiment and aggregate • Experimenter tools eliminate the need for most experimenters to write or read RSpec <?xml version="1.0" encoding="UTF-8"?> <rspecxmlns="http://www.protogeni.net/resources/rspec/2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2 http://www.protogeni.net/resources/rspec/2/request.xsd" type="request" > <node client_id="my-node" exclusive="true"> <sliver_type name="raw-pc" /> </node> </rspec> RSpec for requesting a single node