OneLab An Open Federated Laboratory to evaluate the possible futures of the Internet

1. OneLabAn Open Federated Laboratory to evaluate the possible futures of the Internet Serge Fdida http://www-rp.lip6.fr/~sf/ Université Pierre et Marie Curie – Paris 6 Laboratoire LIP6 – CNRS France SBRC 2008, May 29, Rio de Janeiro

2. Remaining grand challenges in networking: Are there any?

3. Short answer! Pick one : YES NO

4. Is there a future for the INTERNET?

5. Vision • Explore the possible Future(s) of the Internet • Realistic view • Continuous evolution and change • The future Internet might be Polymorphic • Various research projects, scientists and “people” will propose new ideas • Building blocks • Architectures

6. Vision • Networked Systems are predominant, with various forms • Virtual Worlds are emerging • Moving more from connectivity to content • An enabler for service creation • An enabler for competition

7. Changes • Increased heterogeneity of devices and networks • Mobility and Dynamicity • Increased management complexity • Security and Trust • An increasing variety of applications • Managed and unmanaged systems

8. Economical/Social factors • Usage and Services will become predominant • User-centric approach to system design • Other factors than technology will be instrumental • Economics, Social behaviors, Entry cost, Regulation…

10. The Polymorphic Internet : Some Internet Future(s) • The Network is a Database • The (Access) Network is Wireless • The Network is the People • The Network is a global Virtualized resource • They’re all Federated

11. Some observations on recent evolutions • CONTENT, who cares about Packets • Content distribution is the communication rationale • Popular content is likely to be “en route”. No need to fetch it from a server/peer, or, at least doest not make sense to send thousands of unicast streams • Shared (“Data to Many”) • Traffic Engineering moving from flows to services • DPI (Deep Packet Inspection) is becoming available • The MEDIATION router

12. The Network is the people • Services where infrastructure is lacking or damaged • Intermittent connectivity • Multiple access opportunities • A challenge for the Services • Opportunistic networking • DTN approaches

13. Mobility • Always ON is not for the network • Mobility favors interest • Mobility increases capacity • Mobility is very context sensitive • Disturbance • Silence, …

14. Virtualized networked systems • Today, there is already a rationale for going to virtualized servers in Enterprise Networks • The networked system connects Virtualized Resources • Network clients are themselves less persistent (mobile, nomadic, ambient intelligence) • On-demand Networking • Virtualized networks to support a Polymorphic Internet • Federation comes into the big picture • Managing, Securing the virtualized environment

15. Federation conceptwww.one-lab.org • Federation is more than interconnection • API, Policies • Governance, Trust, Economics • Interoperable naming system • Service discovery • Resource management in a Federated environment • A user in a single domain • A domain in a federation • Incentive for federation • Fixed contribution • Reliability, Heterogeneity, Amount of resources • Resource management • A user outside the federation

16. What are our main questions? • How to assess the assumptions and solutions explored by the research projects? • Building a Facility, which affordable long-term vision can we develop? • What is a reasonable starting point? • How to study different transition scenarios? • What are the purposes to be served? • What are the facility-specific research challenges?

17. WARNING! Building a testbed is not REWARDING It requires a lot of resources and is hard to publish Still ….

18. OneLab 1 & 2 Vision OneLab: An Open Federated Laboratory Supporting Network Research for the Future Internet Develop and operate a large facility to support networking research and evaluate design solutions Supports current and emerging architectures Adopts a pragmatic approach: • Evaluates challenges and proposed solutions • Deploys incrementally • Supports the federation concept • Builds towards a long-term objective

19. OneLab History Oct’03 March’04 May’04 Sept’05 Sept’06 Dec’07 OneLab submitted as IST STREP Onelab funded as IST project (Strep), 2 years -3M€ OneLab2 accepted as IST project (IP), 2 years- 10M€ ENEXT NoE Testbeds PlanetLab Europe Initiative PlanetLab meeting in Cambridge NSF GENI Initiative

20. Building The Facility • Research projects are the roots for exploring the future(s) of the Internet • Other proposals might be developed independently (outside ICT) • Develop incentives for research projects (at large) to experiment with their ideas • Lower the entry cost for experimentation • An open and federated facility • Provide some diversity • General and dedicated resources made available • At scale, with international visibility and usage

21. The starting point • Do not start from scratch • Too long to make the “utility function” high enough in the short-medium term • Initialize with existing testbeds • Enforce the federation concept to expect a convergence in the long-term • Assess the usefulness of what is provided regularly enabling a platform for research projects

22. Evaluation • Enforce the projects to evaluate their proposal with some form of experiments • Proof-of-concept • Instrument the experiments and make data public (when possible) • Define “Benchmarking” environments wrt target objectives • even if it is hard, or at least, provide a well-defined set of parameters to be able to reproduce the results • Provide a repository for the data • Liaison with other initiatives at the international level

23. Outline • PlanetLab • OneLab • Services, management and operation

24. PlanetLab overview

25. PlanetLab nodes Single PLC located at Princeton • 842 machines spanning • 416 sites • 35 countries

26. PlanetLab in Brazil • 5 sites and 10 nodes • RNP - Ceara • Universidade Federal de Minas Gerais • RNP - Rio de Janeiro • Federal University of ABC - Santo André • RNP - Rio Grande do Sul

27. Inside a node Node Mgr Owner VM VM1 VM2 VMn … Virtual Machine Monitor (VMM) Kernel Hardware

28. VMM • Linux • significant mind-share • Vserver • scales to hundreds of VMs per node (12MB each) • Scheduling • CPU • fair share per slice (guarantees possible) • link bandwidth • fair share per slice • peak rate limit: set by each site (100Mbps default) • disk • 5GB quota per slice (limit run-away log files) • memory • no limit

29. Sliver Access

30. Zero Slice on nodes

31. Slice 1 with 9 Slivers

32. Slice 2 with 7 slivers

33. Slices

34. Sensors • Sensors are services located on a slice. • Used for Auditing & Monitoring • PlanetFlow • logs every outbound IP flow on every node • retrieves packet headers, timestamps, context ids (batched) • used to audit traffic • aggregated and archived at PLC • SliceStat • has access to kernel-level / system-wide information • accesses /proc via Proper • used by global monitoring services • used to performance debug services

35. Long-Running Services • Content Distribution • CoDeeN: Princeton (serving > 1 TB of data per day) • Internet Measurement • ScriptRoute: Washington, Maryland • DHT • Chord (DHash): MIT • DNS • CoDNS: Princeton • Brokerage Services • Sirius: Georgia (Time and CPU priority) • Monitoring/Discovery Services • CoMon: Princeton

36. User experiments • Research and commercial experiments • Testing a peer-to-peer game architecture, On-demand streaming service: CERNET • Measuring availability to/from multi-homed sites on the Internet: CarnegieMellon • Internet topology measurements: UPMC • Network Security: Columbia • Determine reachability of Google IPs from various parts of the internet: Google • Distributed skype experiments: Maryland

37. Outline • PlanetLab • OneLab • Services, management and operation

38. OneLab Goals • Extend • Extend PlanetLab into new environments, beyond the traditional wired internet. • Deepen • Deepen PlanetLab’s monitoring capabilities. • Operate PlanetLab Europe • Provide a European administration for PlanetLab nodes in Europe. • Federate • With other PlanetLab worldwide

39. ExtendOneLab to New Environments • WiMAX (Université Catholique de Louvain) • UMTS (Università di Napoli, Alcatel Italia) • Wireless ad hoc networks (France Telecom) • Emulated (Università di Pisa) • Based on dummynet • Multihomed (Universidad Carlos III de Madrid)

40. Why Deepen PlanetLab? • Problem: PlanetLab provides limited facilities to make applications aware of the underlying network • PlanetLab consists of end-hosts • Routing between nodes is controlled by the internet (This will change with VINI/GENI) • Applications must currently make their own measurements

41. Why Federate PlanetLab? Federation adds diversity and scale Federation allows each individual component to evolve independently Federation raises Governance issues • What if we want to study a particular wireless technology, and this requires changes to the source code? • What if we wish to change the cost structure for small and medium size enterprises?

42. OneLab Vision for PlanetLab - Reveal the underlying network - Extend into new wired and wireless environments - Deploy and manage PlanetLab-Europe

43. PlanetLab Europe • PlanetLab Europe • Run by UPMC • https://www.planet-lab.eu • Create a European consortium with evolutive Acceptable Use Policies. • Federation with Princeton (PLC) • Expect 195+ European nodes (58 Germany, 24 Poland,..) • support@planet-lab.eu

44. Welcome to PlanetLab Europe https://www.planet-lab.eu

45. PlanetLab Europe Wireless component • Added wireless capabilities to the kernel • Integration of Madwifi drivers on each nodes: • Open issues • Virtualization of Wireless! • « usage model » • Acces Policy : Assume many wireless testbeds to be made available on PlanetLab

46. PlanetLab Europe Wireless component (preliminary) • The node software allow the deployment and test application in wireless mesh multi-hop network. • A node has to be configured with a fixed IP, OLSR, and ad hoc routing table. Wireless node

47. PlanetLab Europe Wireless component • In order to broaden the scope of devices (PDAs, mobile phone,…), the nodes can be PlanetLab Europe software independent if they are connected to a gateway configured with the node software Gateway

48. PlanetLab Europe Wireless component • If no Gateway is configured the user can: • Access to each individual node of the wireless multi-hop mesh network with his ssh key. • Use the configured wireless command. • Launch application (Streaming video, iperf, hping, …). ssh

49. PlanetLab Europe Wireless component • If the Gateway is used: • A PlanetLab Europe user can have access to the monitoring interface on the gateway node. Network topology Link Stability

50. PlanetLab Europe Emulation component • DummynetBox (DBox): • Based on Dummynet • (Emulation component used in EmuLab) • Individual users (slivers) can independently and concurrently set up the characteristics of the emulated link for their experiment.