1. PlanetLab and OneLab Presentation at the GRID 5000 School 9 March 2006 Timur Friedman Université Pierre et Marie Curie Laboratoire LIP6-CNRS PlanetLab slides based on slides provided courtesy of Larry Peterson

2. PlanetLab An open platform for: –testing overlays, –deploying experimental services, –deploying commercial services, –developing the next generation of internet technologies. A set of virtual machines –distributed virtualization –each of 350+ network services runs in its own slice

3. PlanetLab nodes 637 machines spanning 302 sites and 35 countries nodes within a LAN-hop of > 2M users

4. Slices

7. User Opt-in Server NAT Client

8. Per-Node View Virtual Machine Monitor (VMM) Node Mgr Local Admin VM 1 VM 2 VM n …

9. Architecture (1) Node Operating System –isolate slices –audit behavior PlanetLab Central (PLC) –remotely manage nodes –bootstrap service to instantiate and control slices Third-party Infrastructure Services –monitor slice/node health –discover available resources –create and configure a slice –resource allocation

10. 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 Architecture (2)

11. Architecture (3) Node MA NM + VMM node database Node Owner VM SCS SA slice database VM Service Developer

12. Long-Running Services Content Distribution –CoDeeN: Princeton –Coral: NYU –Cobweb: Cornell Internet Measurement –ScriptRoute: Washington, Maryland Anomaly Detection & Fault Diagnosis –PIER: Berkeley, Intel –PlanetSeer: Princeton DHT –Bamboo (OpenDHT): Berkeley, Intel –Chord (DHash): MIT

13. Services (cont) Routing –i3: Berkeley –Virtual ISP: Princeton DNS –CoDNS: Princeton –CoDoNs: Cornell Storage & Large File Transfer –LOCI: Tennessee –CoBlitz: Princeton –Shark: NYU Multicast –End System Multicast: CMU –Tmesh: Michigan

14. Usage Stats Slices: 350 - 425 AS peers: 6000 Users: 1028 Bytes-per-day: 2 - 4 TB –Coral CDN represents about half of this IP-flows-per-day: 190M Unique IP-addrs-per-day: 1M

15. OneLab A potential project, currently under negotiation with the European Commission –Project leader: UPMC/LIP6-CNRS –Technical direction: INRIA Sophia-Antipolis –Other partners: Intel Research Cambridge, Universidad Carlos III de Madrid, Université Catholique de Louvain, Università di Napoli, France Telecom (Lannion), Università di Pisa, Alcatel Italia, Telekomunikacja Polska Goals: –Extend PlanetLab into new environments, beyond the traditional wired internet. –Deepen PlanetLab’s monitoring capabilities. –Provide a European administration for PlanetLab nodes in Europe.

16. Goal: New Environments Problem: PlanetLab nodes are connected to the traditional wired internet. –They are mostly connected to high-performance networks such as Abilene, DANTE, NRENs. –These are not representative of the internet as a whole. –PlanetLab does not provide access to emerging environments. OneLab will place nodes in new environments: –Wireless: WiMAX, UMTS, and wireless ad hoc networks. –Wired: multihomed nodes. –Emulated: for new and experimental technologies.

17. Goal: Deepen Monitoring Problem: PlanetLab provides limited facilities to make applications aware of the underlying network OneLab’s monitoring components –Passive monitoring: Track packets at the routers –Topology monitoring: Provide a view of the route structure

18. PlanetLab Before OneLab

19. PlanetLab After OneLab

20. New Environments

21. Monitoring Capabilities

22. Goal: European Administration Problem: Changes to PlanetLab must come through the administration at Princeton. –PlanetLab in the US is necessarily less responsive to European research priorities. OneLab will create a PlanetLab Europe. –It will federate with PlanetLab in the US, Japan, and elsewhere. –The federated structure will allow: PlanetLab Europe to set policy in accordance with European research priorities, PlanetLab Europe to customize the platform, so long as a common interface is preserved.

23. PlanetLab and GRID 5000 Some goals in common Some differences in architecture Possibilities for cooperation between OneLab and GRID 5000

24. Common goals Test at the scale of the internet, with internet conditions Test new architectures and services –Even radical departures from the current internet PlanetLab a precursor to the GENI initiative

25. Internet GRID 5000 is at the scale of the internet –Reserved fibre to interconnect clusters –Cross-traffic can be injected, if wished –Ability to control and replay experiments PlanetLab works over the internet –Connections between nodes pass via the public internet –Cross-traffic comes from the internet itself Test services in a real setting A challenged environment is interesting –PlanetLab provides services to internet users

26. Clusters GRID 5000 consists of clusters of many machines –To participate in GRID 5000, one signs up with one of the cluster administrators –Access is to university and state-sponsored research labs There are typically two PlanetLab nodes to a site –To participate in PlanetLab, one provides two nodes –University and state-sponsored research labs pay no fees –For-profit organizations pay fees of $25K/yr.+ –Available for use by industry

27. Virtualization GRID 5000 designed for the installation of any OS on top of the hardware of any node –One OS per machine PlanetLab designed for the installation of multiple virtual machines on top of a VMM (virtual machine manager) on any node –VMM currently linux-vserver Could be xen-domain, or other –Virtual machines currently only Linux Eventually could be any suitably adapted OS GRID 5000’s OS could be a VMM, if desired

28. Reservations Users reserve GRID 5000 nodes –No two users have the same node at the same time –Users have access to completely unloaded machines Users share PlanetLab nodes –The load affects the performance –Problems arise close to major conference deadlines –Services allow one to select a subset of nodes based on their load characteristics –Services allow one to make a reservation for higher priority on certain machines

29. Cooperation Test PlanetLab architectures on GRID 5000 –OneLab topology monitoring component will be tested on GRID 5000 Joint work: Pierre Sens and Timur Friedman Test GRID 5000 architectures on PlanetLab? The European Commission invites such forms of cooperation

30. Fin

31. More About PlanetLab

32. PlanetLab Architecture What is the PlanetLab architecture? –more a question of synthesis than cleverness Why is this the right architecture? –non-technical requirements –technical decisions that influenced adoption What is a system architecture anyway? –how does it accommodate change (evolution)

33. Requirements 1)Global platform that supports both short-term experiments and long-running services. –services must be isolated from each other performance isolation name space isolation –multiple services must run concurrently Distributed Virtualization –each service runs in its own slice: a set of VMs

34. Requirements 2)It must be available now, even though no one knows for sure what “it” is. –deploy what we have today, and evolve over time –make the system as familiar as possible (e.g., Linux) Unbundled Management –independent mgmt services run in their own slice –evolve independently; best services survive –no single service gets to be “root” but some services require additional privilege

35. Requirements 3)Must convince sites to host nodes running code written by unknown researchers. –protect the Internet from PlanetLab Chain of Responsibility –explicit notion of responsibility –trace network activity to responsible party

36. Requirements 4)Sustaining growth depends on support for autonomy and decentralized control. –sites have the final say about the nodes they host –sites want to provide “private PlanetLabs” –regional autonomy is important Federation –universal agreement on minimal core (narrow waist) –allow independent pieces to evolve independently –identify principals and trust relationships among them

37. Requirements 5)Must scale to support many users with minimal resources available. –expect under-provisioned state to be the norm –shortage of logical resources too (e.g., IP addresses) Decouple slice creation from resource allocation Overbook with recovery –support both guarantees and best effort –recover from wedged states under heavy load

38. Tension Among Requirements Distributed Virtualization / Unbundled Management –isolation vs one slice managing another Federation / Chain of Responsibility –autonomy vs trusted authority Under-provisioned / Distributed Virtualization –efficient sharing vs isolation Other tensions –support users vs evolve the architecture –evolution vs clean slate

39. Synergy Among Requirements Unbundled Management –third party management software Federation –independent evolution of components –support for autonomous control of resources

40. Architecture (1) Node Operating System –isolate slices –audit behavior PlanetLab Central (PLC) –remotely manage nodes –bootstrap service to instantiate and control slices Third-party Infrastructure Services –monitor slice/node health –discover available resources –create and configure a slice –resource allocation

41. Trust Relationships Princeton Berkeley Washington MIT Brown CMU NYU ETH Harvard HP Labs Intel NEC Labs Purdue UCSD SICS Cambridge Cornell … princeton_codeen nyu_d cornell_beehive att_mcash cmu_esm harvard_ice hplabs_donutlab idsl_psepr irb_phi paris6_landmarks mit_dht mcgill_card huji_ender arizona_stork ucb_bamboo ucsd_share umd_scriptroute … N x N Trusted Intermediary (PLC)

42. Trust Relationships (cont) Node Owner PLC Service Developer (User) 1 2 3 4 1) PLC expresses trust in a user by issuing it credentials to access a slice 2) Users trust to create slices on their behalf and inspect credentials 3) Owner trusts PLC to vet users and map network activity to right user 4) PLC trusts owner to keep nodes physically secure

43. Trust Relationships (cont) Node Owner Mgmt Authority Service Developer (User) 1 2 3 4 1) PLC expresses trust in a user by issuing credentials to access a slice 2) Users trust to create slices on their behalf and inspect credentials 3) Owner trusts PLC to vet users and map network activity to right user 4) PLC trusts owner to keep nodes physically secure Slice Authority 5 6 5) MA trusts SA to reliably map slices to users 6) SA trusts MA to provide working VMs

44. 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 Architecture (2)

45. Architecture (3) Node MA NM + VMM node database Node Owner VM SCS SA slice database VM Service Developer

46. Per-Node Mechanisms Virtual Machine Monitor (VMM) Node Mgr Owner VM VM 1 VM 2 VM n … Linux kernel (Fedora Core) + Vservers (namespace isolation) + Schedulers (performance isolation) + VNET (network virtualization) SliverMgr Proper PlanetFlow SliceStat pl_scs pl_mom

47. VMM Linux –significant mind-share Vserver –scales to hundreds of VMs per node (12 MB each) Scheduling –CPU fair share per slice (guarantees possible) –link bandwidth fair share per slice average rate limit: 1.5Mbps (24-hour bucket size) peak rate limit: set by each site (100Mbps default) –disk 5 GB quota per slice (limit run-away log files) –memory no limit pl_mom resets biggest user at 90% utilization

48. VMM (cont) VNET –socket programs “just work” including raw sockets –slices should be able to send only… well-formed IP packets to non-blacklisted hosts –slices should be able to receive only… packets related to connections that they initiated (e.g., replies) packets destined for bound ports (e.g., server requests) –essentially a switching firewall for sockets leverages Linux’s built-in connection tracking modules

49. Node Manager SliverMgr –creates VM and sets resource allocations –interacts with… bootstrap slice creation service (pl_scs) third-party slice creation & brokerage services (using tickets) Proper: PRivileged OPERations –grants unprivileged slices access to privileged info –effectively “pokes holes” in the namespace isolation –examples files: open, get/set flags directories: mount/unmount sockets: create/bind processes: fork/wait/kill

50. Auditing & Monitoring PlanetFlow –logs every outbound IP flow on every node accesses ulogd via Proper 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

51. Infrastructure Services Brokerage Services –Sirius: Georgia –Bellagio: UCSD, Harvard, Intel –Tycoon: HP Environment Services –Stork: Arizona –Application Manager: Berkeley (UC + Intel) Monitoring/Discovery Services –CoMon: Princeton –PsEPR: Intel

52. Evolution vs Intelligent Design Favor evolution over clean slate Favor design principles over a fixed architecture Specifically… –leverage existing software and interfaces –keep VMM and control plane orthogonal –exploit virtualization vertical: management services run in slices horizontal: stacks of VMs –give no one root (least privilege + level playing field) –support federation (decentralized control)

53. Other Lessons Inferior tracks lead to superior locomotives Empower the user: yum Build it and they (research papers) will come Overlays are not networks PlanetLab: We debug your network From universal connectivity to gated communities If you don’t talk to your university’s general counsel, you aren’t doing network research Work fast, before anyone cares

54. Fin

55. Available CPU Capacity Feb 1-8, 2005 (Week before SIGCOMM deadline)

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

57. 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 Users create accounts with keys, PI activates accounts (logged) 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

58. Slice Creation PLC (SA) VMM NMVM PI SliceCreate( ) SliceUsersAdd( ) User SliceAttributeSet( ) SliceGetTicket( ) VM …............ (distribute ticket to slice creation service: pl_scs) SliverCreate(rspec)

59. Brokerage Service PLC (SA) VMM NMVM SliceAttributeSet( ) SliceGetTicket( ) VM …............ (distribute ticket to brokerage service) rcap = PoolCreate(rspec) Broker

60. Brokerage Service (cont) PLC (SA) VMM NMVM …............ (broker contacts relevant nodes) PoolSplit(rcap, slice, rspec) VM User BuyResources( ) Broker