1 GENI: Global Environment for Network Innovations Jennifer Rexford Princeton University

Slides:



Advertisements
Similar presentations
VINI and its Future Directions
Advertisements

INDIANAUNIVERSITYINDIANAUNIVERSITY GENI Global Environment for Network Innovation James Williams Director – International Networking Director – Operational.
Network Virtualization Nick Feamster, Georgia Tech Lixin Gao, UMass Amherst Jennifer Rexford, Princeton NSF NeTS-FIND PI Meeting.
VINI: Virtual Network Infrastructure
Cabo: Concurrent Architectures are Better than One Nick Feamster, Georgia Tech Lixin Gao, UMass Amherst Jennifer Rexford, Princeton.
VINI Overview. PL-VINI: Prototype on PlanetLab PlanetLab: testbed for planetary-scale services Simultaneous experiments in separate VMs –Each has root.
My Experience Writing an NSF NeTS FIND Proposal Nick Feamster Georgia Tech.
FIND John Wroclawski USC ISI IEEE CCW - October 2005 Good Morning.
INTRODUCTION TO NETWORK VIRTUALIZATION Mosharaf Chowdhury Member, eNVy Project Wednesday, May 14, 2008 University of Waterloo - eNVy 1.
Jennifer Rexford Princeton University MW 11:00am-12:20pm Network Virtualization COS 597E: Software Defined Networking.
PlanetLab Architecture Larry Peterson Princeton University.
GENI: Global Environment for Networking Innovations Larry Landweber Senior Advisor NSF:CISE Joint Techs Madison, WI July 17, 2006.
Extensible Networking Platform IWAN 2005 Extensible Network Configuration and Communication Framework Todd Sproull and John Lockwood
1 In VINI Veritas: Realistic and Controlled Network Experimentation Jennifer Rexford with Andy Bavier, Nick Feamster, Mark Huang, and Larry Peterson
1 VINI: Virtual Network Infrastructure Jennifer Rexford Princeton University
1 GENI: Global Environment for Network Innovations Jennifer Rexford Princeton University
VROOM: Virtual ROuters On the Move Jennifer Rexford Joint work with Yi Wang, Eric Keller, Brian Biskeborn, and Kobus van der Merwe
RIT Campus Data Network. General Network Statistics Over 23,000 wired outlets Over 14,500 active switched ethernet ports > 250 network closets > 1,000.
1 GENI: Global Environment for Network Innovations Jennifer Rexford Princeton University
An Overlay Data Plane for PlanetLab Andy Bavier, Mark Huang, and Larry Peterson Princeton University.
1 GENI: Global Environment for Network Innovations Jennifer Rexford On behalf of Allison Mankin (NSF)
1 VINI: Virtual Network Infrastructure Jennifer Rexford Princeton University
1 VINI: Virtual Network Infrastructure Jennifer Rexford Princeton University
1 VINI: Virtual Network Infrastructure Jennifer Rexford Princeton University Joint with Andy Bavier, Nick Feamster, Lixin.
Internet In A Slice Andy Bavier CS461 Lecture.
1 Next-Generation Network Research Facilities Jennifer Rexford Princeton University
The End of Internet Architecture Author: Timothy Roscoe Presented by Gross, Zhaosheng Zhu.
In VINI Veritas Realistic and Controlled Network Experimentation Andy Bavier Nick Feamster* Mark Huang Larry Peterson Jennifer Rexford Princeton University.
The Future of Internet Research Scott Shenker (on behalf of many networking collaborators)
Network Virtualization Jennifer Rexford Advanced Computer Networks Tuesdays/Thursdays 1:30pm-2:50pm.
1 GENI: Global Environment for Network Innovations Jennifer Rexford Princeton University See for.
The Future of the Internet Jennifer Rexford ’91 Computer Science Department Princeton University
Backbone Support for Host Mobility: A Joint ORBIT/VINI Experiment Jennifer Rexford Princeton University Joint work with the ORBIT team (Rutgers) and Andy.
Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking.
C OLUMBIA U NIVERSITY Lightwave Research Laboratory Embedding Real-Time Substrate Measurements for Cross-Layer Communications Caroline Lai, Franz Fidler,
Morteza Yousefi University of Science & Technology of Mazandaran Network Virtualization 1 of 22 Network Virtualization.
Hosting Virtual Networks on Commodity Hardware VINI Summer Camp.
GENI: Global Environment for Network Innovations March 10, 2006 Larry Peterson Princeton University.
FIND experimental requirements David D. Clark. FIND Future Internet Design (FIND) is an NSF program (now folded in to NetSE) to envision the Internet.
Software-Defined Networks Jennifer Rexford Princeton University.
Eric Keller, Evan Green Princeton University PRESTO /22/08 Virtualizing the Data Plane Through Source Code Merging.
1 Cabo: Concurrent Architectures are Better than One Jennifer Rexford Princeton University Joint work with Nick Feamster.
GENI: Global Environment for Networking Innovations Allison Mankin (for the GENI Team) CISE/NSF Rest of GENI Team: Guru Parulkar, Paul.
GENI: Catalyzing Network Research May 31, 2007 Larry Peterson Princeton University.
Software-defined Networking Capabilities, Needs in GENI for VMLab ( Prasad Calyam; Sudharsan Rajagopalan;
1 Supporting the development of distributed systems CS606, Xiaoyan Hong University of Alabama.
GENI: Global Environment for Network Investigations Tom Anderson (and the GENI planning committee) FIND GENI.
Virtual Private Ad Hoc Networking Jeroen Hoebeke, Gerry Holderbeke, Ingrid Moerman, Bard Dhoedt and Piet Demeester 2006 July 15, 2009.
A Framework for Internetworking Heterogeneous High-Performance Networks via GMPLS and Web Services Xi Yang, Tom Lehman Information Sciences Institute (ISI)
Department of Energy Office of Science ESCC & Internet2 Joint Techs Workshop Madison, Wisconsin.July 16-20, 2006 Network Virtualization & Hybridization.
Vytautas Valancius, Nick Feamster, Akihiro Nakao, and Jennifer Rexford.
Chapter 7 Backbone Network. Announcements and Outline Announcements Outline Backbone Network Components  Switches, Routers, Gateways Backbone Network.
1 Testbeds Breakout Tom Anderson Jeff Chase Doug Comer Brett Fleisch Frans Kaashoek Jay Lepreau Hank Levy Larry Peterson Mothy Roscoe Mehul Shah Ion Stoica.
Advanced Networks: The Past and the Future – The Internet2 Perspective APAN 7 July 2004, Cairns, Australia Douglas Van Houweling, President & CEO Internet2.
Evolving Toward a Self-Managing Network Jennifer Rexford Princeton University
Virtualization as Architecture - GENI CSC/ECE 573, Sections 001, 002 Fall, 2012 Some slides from Harry Mussman, GPO.
1 Revision to DOE proposal Resource Optimization in Hybrid Core Networks with 100G Links Original submission: April 30, 2009 Date: May 4, 2009 PI: Malathi.
Scrapping the Internet Presented by Dhaval Joshi.
“End to End VoIP“ The Challenges of VoIP Access to the Enterprise Charles Rutledge VP Marketing Quintum Technologies
Active Networks Jennifer Rexford. Nice Quotation from the Tennenhouse Paper There is presently a disconnect between what users consider to be “inside”
The Internet2 Network and LHC Rick Summerhill Director Network Research, Architecture, and Technologies Internet2 LHC Meeting 23 October 2006 FERMI Lab,
Instructor Materials Chapter 7: Network Evolution
Multi-layer software defined networking in GÉANT
Ahmed Saeed†, Mohamed Ibrahim†, Khaled A. Harras‡, Moustafa Youssef†
Welcome Network Virtualization & Hybridization Thomas Ndousse
Oracle Solaris Zones Study Purpose Only
GGF15 – Grids and Network Virtualization
Aled Edwards, Anna Fischer, Antonio Lain HP Labs
Chapter 7 Backbone Network
GENI Global Environment for Network Innovation
Presentation transcript:

1 GENI: Global Environment for Network Innovations Jennifer Rexford Princeton University

2 Outline Networking research challenges –Security, economic incentives, management, layer-2 technologies Importance of building and deploying –Bridging the gap between simulation/testbeds and real deployment Global Environment for Network Innovations (GENI) –Major NSF initiative to support experimental networking research –Key ideas: virtualization, programmability, and user opt-in GENI backbone design –Programmable routers, flexible optics, and connection to Internet Virtual Network Infrastructure (VINI) –Initial experimental network facility in NLR and Abilene Conclusions

3 Is the Internet broken? It is great at what it does. –Everyone should be proud of this. –All sorts of things can be built on top of it. But… –Security is weak and not getting better. –Availability continues to be a challenge. –It is hard to manage and getting harder. –It does not handle mobility well. –A long list, once you start…

4 Challenges Facing the Internet Security and robustness –Naming and identity –Availability Economic incentives –Difficulty of providing end-to-end services –Commoditization of the Internet infrastructure Network management –No framework in the original Internet design –Tuning, troubleshooting, accountability, … Interacting with underlying network technologies –Advanced optics: dynamic capacity allocation –Wireless: mobility, dynamic impairments –Sensors: small embedded devices at large scale

5 FIND: Future Internet Design NSF research initiative –Requirements for global network of years out? –Re-conceive the network, if we could design from scratch? Conceive the future, by letting go of the present: –This is not change for the sake of change –Rather, it is a chance to free our minds –Figuring out where to go, and then how to get there Perhaps a header format is not the defining piece of a new architecture –Definition and placement of functionality –Not just data plane, but also control and management –And division between end hosts and the network

6 The Importance of Building Systems-oriented computer science research needs to build and try out its ideas to be effective –Paper designs are just idle speculation –Simulation is only occasionally a substitute We need: –Real implementation –Real experience –Real network conditions –Real users –To live in the future

7 Need for Experimental Facility AnalysisSimulation / EmulationExperiment At Scale Deployment (models)(code) (results) (measurements) Goal: Seamless conception-to-deployment process

8 Today’s Tools Have Limitations Simulation based on simple models –Topologies, administrative policies, workloads, failures… Emulation (and “in lab” tests) are similarly limited –Only as good as the models Traditional testbeds are targeted –Not cost-effective to test every good idea –Often of limited reach –Often with limited programmability Testbed dilemma –Production network: real users, but hard to make changes –Research testbed: easy to make changes, but no users

9 Bridging the Chasm This chasm is a major barrier to realizing the future designs Maturity Time Foundational Research Simulation and Research Prototypes Small Scale Testbeds Deployed Future Internet Global Experimental Facility

10 GENI Experimental facility –MREFC proposal to build a large-scale facility –Jointly from NSF’s CS directorate, & research community –We are currently at the “Conceptual Design” stage –Will eventually require Congressional approval Global Environment for Network Innovations –Prototyping new architectures –Realistic evaluation –Controlled evaluation –Shared facility –Connecting to real users –Enabling new services See

11 Three Key Ideas in GENI Virtualization –Multiple architectures on a shared facility –Amortizes the cost of building the facility –Enables long-running experiments and services Programmable –Enable prototyping and evaluation of new architectures –Enable a revisiting of today’s “layers” Opt-in on a per-user / per-application basis –Attract real users Demand drives deployment / adoption –Connect to the Internet To reach users, and to connect to existing services

12 Slices

13 Slices

14 User Opt-in Client Server Proxy

15 Realizing the Ideas Slices embedded in a substrate of resources –Physical network substrate Expandable collection of building block components Nodes / links / subnets –Software management framework Knits building blocks together into a coherent facility Embeds slices in the physical substrate Builds on ideas in past systems –PlanetLab, Emulab, ORBIT, X-Bone, …

16 National Fiber Facility

17 + Programmable Routers

18 + Clusters at Edge Sites

19 + Wireless Subnets

20 + ISP Peers ISP 2 ISP 1

21 Closer Look Internet backbone wavelength backbone switch Sensor Network Edge Site Wireless Subnet Customizable Router Dynamic Configurable Swith

22 GENI Substrate: Summary Node components –Edge devices –Customizable routers –Optical switches Bandwidth –National fiber facility –Tail circuits Wireless subnets –Urban –Wide-area 3G/WiMax –Cognitive radio –Sensor net –Emulation

23 GENI Management Core GMC Management Services Substrate Components - name space for users, slices, & components - set of interfaces (“plug in” new components) - support for federation (“plug in” new partners)

24 Hardware Components Substrate HW

25 Virtualization Software Virtualization SW Substrate HW Virtualization SW Substrate HW Virtualization SW Substrate HW

26 Component Manager Substrate HW CM Virtualization SW CM Virtualization SW CM Virtualization SW

27 GENI Management Core (GMC) Resource ControllerAuditing Archive Slice Manager GMC node control sensor data CM Virtualization SW Substrate HW CM Virtualization SW Substrate HW CM Virtualization SW Substrate HW slice_spec (object hierarchy)

28 Federation... GMC

29 User Front-End(s)... Front-End (set of management services) GUI GMC provisioning service file & naming service information plane

30 Virtualization in GENI Multiple levels possible –Different level required by different experiments –Different level depending on the technology Example “base cases” –Virtual server (socket interface / overlay tunnels) –Virtual router (virtual line card / static circuits) –Virtual switch (virtual control interface / dynamic circuits) –Virtual AP (virtual MAC / fixed spectrum allocation) Specialization –The ability to install software in your own virtual-*

31 Distributed Services in GENI Goals –Complete the GENI management story –Lower the barrier-to-entry for researchers (students) Example focus areas –Provisioning (slice embedder) –Security –Information plane –Resource allocation –Files and naming –Topology discovery –Development tools –Interfacing with the Internet, and IP

32 GENI Security Limits placed on a slice’s “reach” –Restricted to slice and GENI components –Restricted to GENI sites –Allowed to compose with other slices –Allowed to interoperate with legacy Internet Limits on resources consumed by slices –Cycles, bandwidth, disk, memory –Rate of particular packet types, unique addrs per second Mistakes (and abuse) will still happen –Auditing will be essential –Network activity slice responsible user(s)

33 Success Scenarios Change the research process –Sound foundation for future network architectures –Experimental evaluation, rather than paper designs Create new services –Demonstrate new services at scale –Attract real users Aid the evolution of the Internet –Demonstrate ideas that ultimately see real deployment –Provide architectural clarity for evolutionary path Lead to a future global network –Purist: converge on a single new architecture –Pluralist: virtualization supporting many architectures

34 Working Groups to Flesh Out Design Research (Dave Clark and Scott Shenker) –Usage policy / requirements / instrumentation Architecture (Larry Peterson and John Wroclawski) –Define core modules and interfaces Backbone (Jen Rexford and Dan Blumenthal) –Fiber facility / routers & switches / tail circuits / peering Wireless (Dipankar Raychaudhuri and Deborah Estrin) –RF technologies / deployment Services (Tom Anderson, Reiter) –Edge sites / infrastructure and underlay services Education –Training / outreach / course development

35 GENI Backbone Requirements Programmability –Flexible routing, forwarding, addressing, circuit set-up, … Isolation –Dedicated bandwidth, circuits, CPU, memory, disk Realism –User traffic, upstream connections, propagation delays, equipment failure modes, … Control –Inject failures, create circuits, exchange routing messages Performance –High-speed packet forwarding and low delays Security –Preventing attacks on the Internet, and on GENI itself

36 A Researcher’s View of GENI Backbone Virtual network topology –Nodes and links in a particular topology –Resources and capabilities per node/link –Embedded in the GENI backbone Virtual router and virtual switch –Abstraction of a router and switch per node –To evaluate new architectures (routing, switching, addressing, framing, grooming, layering, …) GENI backbone capabilities evolve over time –To realize the abstractions at finer detail –To scale to a larger number of experiments

37 Creating a Virtual Topology Some links and nodes unused Some links created by cutting through other nodes Allocating a fraction of a link and node

38 GENI Backbone

39 GENI Backbone Node Components Phase 0 – General purpose blade server –Single node with collection of assignable resources –Virtual Router may be assigned VM, blade or >1 blades Phase 1 – Adding higher performance components –Assignable Network Processor blades and FPGA blades –NPs also used for I/O for better control of I/O bandwidth Phase 2 – Adding reconfigurable cross-connect –Enable experiments with configurable transport layer –Provide “true circuits” between backbone virtual routers Phase 3 – Adding dynamic optical switch –Dynamic optical switch with programmable groomer and framer, and reconfigurable add/drop multiplexers

40 GENI Backbone Node Components Phase 0 – General purpose blade server –Node with collection of assignable resources –Virtual Router may be assigned a virtual machine, blade, or multiple blades Mgmt. Proc. Switch P1P1... P2P2 P3P3 PnPn Mgmt. Proc.

41 GENI Backbone Node Components Phase 1 – Adding higher performance components –Assignable Network Processor blades and FPGA blades –NPs also used for I/O for better control of bandwidth –ATCA chassis and blades GigE Links Mgmt. Proc. Switch PE 1... PE 2 PE n LC k Mgmt. Proc. GP Blade Server LC 1

42 GENI Backbone Node Components Phase 2 – Reconfigurable cross-connect –Enable experiments with configurable transport layer –Provide “true circuits” between backbone virtual routers –Cut-through traffic circumvents the router VX VR Customizable Router 10GE+VLAN 1 GE Wavelength tunable transponders /combiner WDM Fiber Programmable Cross-Connect/ Groomer Control Plane

43 GENI Backbone Node Components Phase 3 – Adding dynamic optical switch –Dynamic optical switch with programmable groomer and framer, and reconfigurable add/drop multiplexers –Maleable bandwidth –Arbitrary framing VC1 Customizable Router 10GE+VLAN 1 GE Wavelength tunable transponders Programmable Cross-Connect/ Groomer Control Plane ROADM

44 GENI Backbone Software Component manager and virtualization layer –Abstraction of virtual router and virtual switch –Setting scheduling parameters for subdividing resources Multiplexers for resources hard to share –Single BGP session with the outside world –Single interface to an element-management system Exchanging traffic with the outside world –Routing and forwarding software to evaluate & extend –VPN servers and NATs at the GENI/Internet boundary Libraries to support experimentation –Specifying, controlling, and measuring experiments –Auditing and accounting to detect misbehavior

45 Feasibility Industrial trends and standards –Advanced Telecom Computing Architecture (ATCA) –Network processors and FPGAs –SONET cross connects and ROADMs Open-source networking software –Routing protocols, packet forwarding, network address translation, diverting traffic to an overlay Existing infrastructure –PlanetLab nodes, software, and experiences –National Lambda Rail and Abilene backbones

46 VINI: Step Toward GENI Backbone Virtual Network Infrastructure (VINI) –Multiple network experiments in parallel –Connections to end users and upstream providers –Supporting Internet protocols and new designs VINI as an initial experimental platform –Support researchers doing network experiments –Explore software challenges of building GENI backbone GENI will have a much wider scope –Programmable hardware routers –Flexible control of the optical components –Wireless and sensor networks at the edge

47 Network Infrastructure Network topology –Points of Presence –Link bandwidth –Upstream connectivity Two backbones –Abilene Internet2 –National Lambda Rail

48 Building Virtual Networks Physical nodes –Initially, high-end computers –Later, network processors and FPGAs Virtual routers (a la PlanetLab) –Multiple virtual servers on a single node –Separate shares of resources (e.g., CPU, bandwidth) –Extensions for resource guarantees and priority

49 Building Virtual Links Creating the illusion of interfaces –Create a tunnel for each link in the topology –Assign IP addresses to the end-points of tunnels –Match tunnels with one-hop links in the real topology

50 Building Multiple Virtual Topologies Separate topology per experiment –Routers are virtual servers –Links are a subset of possible tunnels Creating a customized environment –Running User Mode Linux (UML) in a virtual server –Configuring UML to see multiple interfaces –Enables running the routing software “as is” Operating System RRRRR

51 Overcoming Efficiency Challenges Packet forwarding must be fast –But, we are doing packet forwarding in software –And don’t want the extra overhead of UML Solution: separate packet forwarding –Routing protocols running within UML –Packet forwarding running outside of UML UML Click XORP XORP: routing software Click: forwarding software

52 Carrying Real User Traffic Users opt in to VINI –User runs VPN client –Connects to VINI node External Internet hosts –VINI connects to Internet –Apply NAT at boundary UML Click Client Server UDP tunnels XORP Open VPN Network Address Translation routing-protocol messages VINI

53 Example VINI Experiment Configure VINI just like Abilene –VINI node per PoP –VINI link per inter-PoP link –Routing configuration as real routers Network event –Inject link failure between two PoPs –… in midst of an ongoing file transfer Measuring routing convergence –Packet monitoring of the data transfer –Active probes of round-trip time & loss –Detailed view of effects on data traffic

54 VINI Current Status Initial Abilene deployment –Eleven sites –Nodes running XORP and Click on UML Upcoming deployment –Six sites in National Lambda Rail –… with direct BGP sessions with CRS-1 routers –Dedicated 1 Gbps bandwidth between Abilene sites In the works –Upstream connectivity via a commercial ISP in NYC –Speaking interdomain routing with the Internet Initial write-up:

55 Conclusions Future Internet poses many research challenges –Security, network management, economics, layer-2, … Research community should rise to the challenge –Conceive of future network architectures –Prototype and evaluate architectures in realistic settings Global Environment for Network Innovations (GENI) –Facility for evaluating new network architectures –Virtualization, programmability, and user opt-in GENI backbone design –Fiber facility, tail circuits, and upstream connectivity –Programmable router and dynamical optical switch VINI prototype –Concrete step along the way to the GENI backbone