1. OneLab An 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. 4 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. 5 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. 6 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. 7 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…

9. 8

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

11. 10 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. 11 Some observations on recent evolutions APPLICATION Oriented Architectures – Emergence of SOA (Service Oriented Applications) – Fast growth of the Publish & Subscribe model (PubSub) – Companies are using Enterprise Service Buses (ESBs) and Federation of ESBs; XML based routers exists, IBM ODR, CISCO AON, … – Emergence of Web 2.0, an “architecture of participation” – XML appears as a reference point – Mobility, you want your content to follow you – Competition with broadcasters, services provided by Netvibes and others ….

13. 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

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

15. 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

16. 15 Virtualization Concepts for service virtualization are globally known, but not yet widely tested or deployed. See PlanetLab and new projects such as 4WARD, ONELAB2 Virtualization for large scale networking, wireless networks, security, and e-science Suited for heterogeneous systems Concurrent architectures are better than one (the CABO approach, “routing in a slice”)

17. 16 Federation concept www.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

18. 17 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?

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

20. 19 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

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

22. 21 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

23. 22 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

24. 23 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

25. 24 Development cycles Facility Steering Committee Facility Architects Research community Projects/WG Objectives Priorities Dissemination Developments Integration Dissemination Ideas Usage Methodologies production Requirements Specifications Fireworks

26. 25 Facility evolution Priorities Utility function Selected Test-beds Integrated only if mature New Functionalities API, Policies Governance Pricing Federation FIRE

27. 26 Outline PlanetLab OneLab Services, management and operation

28. 27 PlanetLab An open platform for – Testing overlays (network build on top of one or more existing networks) – Deploying experimental/commercial services – Developing the next generation of internet technologies Global platform that supports both short-term experiments and long-running services. Experiments on PlanetLab figure in many papers at major networking conferences

29. 28 PlanetLab overview

30. 29 PlanetLab nodes 842 machines spanning 416 sites 35 countries Single PLC located at Princeton

31. 30 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

32. 31 Inside a node Virtual Machine Monitor (VMM) Node Mgr Owner VM VM 1 VM 2 VM n … Kernel Hardware

33. 32 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

34. 33 Node requirement

35. 34 Sliver Access

36. 35 Zero Slice on nodes

37. 36 Slice 1 with 9 Slivers

38. 37 Slice 2 with 7 slivers

39. 38 Slices

40. 39 PlanetLab design Database server – Primary information store – Nodes, users, slices API server – Database frontend – Programatic interface Web server – API frontend – Administration Boot server – Software distribution Node – PlanetLab kernel – Node Manager

41. 40 Node Boot/Install NodePLC (MA) Boot Server 1. Boots from BootCD (Linux loaded) 2. Hardware initialized 3. Read network config. from floppy 7. Node key read into memory from floppy 4. Contact PLC (MA) 6. Execute boot mgr Boot Manager 8. Invoke Boot API 10. State = “install”, run installer 11. Update node state via Boot API 13. Chain-boot node (no restart) 14. Node booted 9. Verify node key, send current node state 12. Verify node key, change state to “boot” 5. Send boot manager

42. 41 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

43. 42 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

44. 43 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

45. 44 Outline PlanetLab OneLab Services, management and operation

46. 45 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

47. 46 Extend OneLab 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)

48. 47 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

49. 48 OneLab Monitoring Components Passive monitoring (Technical adviser Intel Research) – Track packets at the routers – Use CoMo boxes located within DANTE Active monitoring (U. P. & M. Curie) – Provide a view of the route structure – Increase the scalability of wide distributed traceroute (traceroute@home)traceroute@home – Reduce traceroute deficiencies on load balanced path (Paris traceroute)

50. 49 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?

51. 50 PlanetLab Today - A set of end-hosts - A limited view of the underlying network - Built on the wired internet

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

53. 52 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 support@planet-lab.eu

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

55. 54 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

56. 55 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

57. 56 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

58. 57 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

59. 58 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

60. 59 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.

61. 60 PlanetLab Europe Emulation component Dummynet API: – Configure and install the DBox on a site. – Assign node, slivers to the DBox. – Load emulation configuration file to emulate the wireless link according to the features requested by the users.

62. 61 PlanetLab Europe Emulation component Configuration of the DBox: – Add sliver/nodes on a Dbox with the DummyNet API methods located on PLE. AddDBox

63. 62 PlanetLab Europe Emulation component Configuration of the DBox: – Configuration of the emulated wireless link (802.11g, 1Mbps, 38dB) on the Dbox with netconfig program. netconfig

64. 63 PlanetLab Europe Emulation component DBox experiment using hping: – The user can use the hping application on his sliver through an ssh connection. ssh

65. 64 PlanetLab Europe Emulation component DBox monitoring : – The DBox continuously monitor the traffic flowing through the interface and report on web page dynamically.

66. 65 Progress on Deepening CoMo is now OneLab-aware, has better scripting – CoMo allows one to write scripts to track one’s own packets as they pass measurement boxes within the network Deploying traceroute@home, a distributed topology-tracing system – Made fundamental improvements to traceroute to correct errors introduced by network load balancing (new tool: Paris traceroute)

67. 66 Goal: Federate Before: a homogeneous system

68. 67 Goal: Federate After: a heterogeneous set of systems

69. 68 Federation concept 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

70. 69 Federation requirements Universal agreement on minimal core (narrow waist) Allow independent pieces to evolve independently Identify principals and trust relationships among them

71. 70 Progress on Federation Jointly developed PlanetLab v4 with Princeton – Allows PLCs (PlanetLab Centrals) to federate – Any user is offered the illusion of a global platform – And can thus create slices as if it was a single testbed – Through a single interface Paradigm – One-to-one peering (n-square trust relationship) – Each PLC has its own database (nodes, users, slices..) – And keeps data from other PLC’s – Slice attributes (grant of resources) remains local: PLE decides how to use resources from its own nodes Running an embryonic PlanetLab Europe – Peering PLE-PLC operational for about a year

72. 71 Federation mechanism

73. 72 Developing the Vision OneLab should be developed as a multi-year facility – Onelab2 (9/08-9/10) Based on three pillars – Platform (development, operations) – Tools (monitoring) – Customers (users and research targets) Liaison with “pilot” projects – Haggle & ANA (SAC), PSIRP (Content), 4WARD (Future Internet) PlanetLab Europe (PLE) will grow over the years – Tools found mature are integrated from OneLab2 into PLE Cooperation with PlanetLab_US/ORBIT/VINI, PlanetLab Japan, FEDERICA, NICTA (Australia), Plans with GLabs

74. 73 OneLab2 Innovations (partial list) Provide embedded passive & active measurement technologies Support wireless integration and develop management tools Provide infrastructural support for large-scale data-centric networking research (CDN, Pub-Sub, Routing in a slice) Integrate Opportunistic Networking and DTN platforms through the SAC Gateway Establish methodology to compare networking experiments in non controllable environments Explore and implement resource management for a single domain and the federation, as well as incentives for sharing Data representation of the variety of resources Of course: operations, integration and maintenance

75. 74 OneLab2 Organisation

76. 75 Governance A need for enforcing cooperation between the main actors Cooperation with – EU (Eiffel, Federica/GEANT) – GENI, Japan, Private testbeds – Explore China, Korea, Brazil, …. Pricing/Charging issues – Research bodies, Research projects, SME’s, Large companies Legal and IPR issues

77. 76 Outline PlanetLab OneLab Services, management and operation

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

79. 78 PlanetLab Europe Terminology and Roles Site: Physical location where PlanetLab nodes are located Node: Dedicated server that runs components of PlanetLab services. Slice: a set of allocated resources distributed across PlanetLab. To most users, a slice means UNIX shell access to a number of PlanetLab nodes Principal Investigator (PI): The PIs at each site are responsible for managing slices and users at each site. PIs are legally responsible for the behaviour of the slices that they create. Technical Contact (Tech Contact): Each site is required to have at least one Technical Contact who is responsible for installation, maintenance, and monitoring of the site's nodes. User: Anyone who develops and deploys applications on PlanetLab.

80. 79 Chain of Responsibility Join Request PI submits Consortium paperwork and requests to join PI Activated PLC verifies PI, activates account, enables site (logged) User Activated The new site migrate to PLE. Nodes Added to Slices Users add nodes to their slice (logged) Slice Traffic Logged Experiments generate traffic (logged by PlanetFlow) Traffic Logs Centrally Stored PLC periodically pulls traffic logs from nodes Slice Created PI creates slice and assigns users to it (logged) Network Activity Slice Responsible Users & PI Users create accounts with keys, PI activates accounts (logged) User Activated

81. 80 Joining PlanetLab Europe PlanetLab Europe will create its own consortium in order to create and validate membership agreement (contract). At the moment new sites have to sign a membership agreement with Princeton. European sites that are already part of PLC can migrate their site without any new contract creation.

82. 81 Joining PlanetLab Europe

83. 82 Joining PlanetLab Europe

84. 83 PlanetLab Europe Site creation How to join? – Just connect to https://planet- lab.eu and fill in the “site registration” form

85. 84 PlanetLab Europe Site creation Warning: there are fields that should be unique across all federated PLC must – Login_base must be unique!!

86. 85 PlanetLab Europe Create an account register into the PlanetLab Europe joining users page (select your site, email, status) – The PI of your site will confirm your account and slice creation by mail.

87. 86 PlanetLab Europe User Account Configuration

88. 87 PlanetLab Europe User Account Configuration Create a SSH private/public key pair, use the ssh-keygen program – ssh-keygen -t rsa – A private key named id_rsa and a public key named id_rsa.pub are generated at default in the.ssh/ on your home directory. - Upload your key in your user account.

89. 88 PlanetLab Europe Creates a slice The PI at your site should validate your slice

90. 89 PlanetLab Europe Manages your slice

91. 90 PlanetLab Europe Manages your slice

92. 91 PlanetLab Europe Node creation

93. 92 PlanetLab Europe Monitor the node status Use CoMon: http://comon.cs.princeton.edu/

94. 93 Monitoring Node trafic with PlanetFlow

95. 94 Monitoring Node trafic with PlanetFlow

96. 95 Resource allocation and provisioning Problem – Many PlanetLab nodes are down or congested Needed – Incentives for infrastructure/resource contributions (provisioning) Question – How to allocate resources in case of congestion?

97. 96 Current situation

98. 97 Uptime

99. 98 Avg. CPU load

100. 99 Sites behaviour Determine four categories of sites behaviour: – Good: Site have good standing nodes and usage (green, yellow) – Donners: Site has working nodes but no usage (blue). – Leaches: Site is down, but using others' resources (Red) – Down: site is down, but no usage (Black)

101. 100 Resource allocation Existing solutions – Provision: simple contribution rule (Min. 2 nodes) – Allocation: (almost) unlimited consumption, equal sharing

102. 101 PlanetLab Resource monitoring Node Manager – monitor slice/node health – discover available resources – create and configure a slice Content Distribution Network for monitoring the health of PlanetLab – CoTop: activity monitoring tool for PlanetLab. – CoMon, a Web-based general node/slice monitor that monitors most PlanetLab nodes.

103. 102 Owner 1 Owner 2 Owner 3 Owner N... Slice Authority Management Authority Software updates Auditing data Create slices... U S E R S PlanetLab Nodes Service Developers Request a slice New slice ID Access slice Identify slice users (resolve abuse) Learn about nodes Node Manager mechanism

104. 103 A rule-based approach Sites with higher (effective) contribution should be granted a higher service level Exploring a Differentiated service approach – Ref: Resource Provision and Allocation in shared Network Testbed Infrastructures : Panayotis Antoniadis in ROADS 2008

105. 104 Objective of the Topology information component Provide information concerning – The underlying network topology (IP/AS-Level) Add two additional measurement subcomponents. – Active measurement subcomponent Traceroute@home: IP-level route traces – AS-level subcomponent BGP guided probing: BGP communities Allow IP to AS mapping. Improve the monitoring capability – Allow applications to query the topology information component. TopHat API

106. 105 PlanetLab Articles You can find the main articles related to PlanetLab: – https://www.planet-lab.org/doc/pdn PlanetLab: An Overlay Testbed for Broad-Coverage Services, Brent Chun, David Culler, Timothy Roscoe, Andy Bavier, Larry Peterson, Mike Wawrzoniak, and Mic Bowman, January 2003. Appears in ACM Computer Communications Review, vol. 33, no. 3, July 2003, a special issue on tools and technologies for networking research and education. An End-to-End Approach to Globally Scalable Programmable Networking, Terry Moore, Micah Beck, and James S. Plank, September 2004. Appears in the Proceedings of the Workshop on Future Directions in Network Architecture (FDNA'03), Karlsruhe, Germany, August 2003

107. European initiative The FIRE - Future Internet Research and Experimentation- Initiative 7 th Framework Programme ICT call 2, Objective 1.6 “New Paradigms and Experimental Facilities”. – 14 Testbeds and Research projects 40 Meuros funding at first call Starting now See – http://cordis.europa.eu/fp7/ict/fire/launch.html http://cordis.europa.eu/fp7/ict/fire/launch.html – http://www.ict-fireworks.eu 106

108. 107 Messages … To much hope to re-invent the Internet – The disappearing internet – The Polymorphic Internet Designing the future – Back to fundamentals – Support experimentally-driven research – Tightly associated to research projects Explore the Federation concept

109. 108 www.one-lab.org OneLab PlanetLab Europe www.planet-lab.eu JOIN US!