1. PlanetLab Inspiration and Partner for ENGINE Jiří Navrátil jiri@cesnet.cz

2. Talk overview First set of questions What is the relation ENGINE and PlanetLab Convergence of ENGINE and NREN infrastructure Second set of questions How to understand ENGINE a new sort of testbed

3. GENI starting in the US and Europe

4. My impression of it and first set of questions Too general picture to understand it What is main difference ENGINE and the other testbeds ? Who are the main users and main purpose of ENGINE ? if computer scientists, they are sitting in the University campuses How to connect them into the ENGINE ? If new Network applications Who are its users, who provide the servers ? Why the principles used in PlanetLab are the key points for GENI ?

6. PlanetLab main goals PlanetLab is concorcium of the Universities and academic institutions established in 2002 by 3 US universities (UC Berkeley, UofWashington, and Princeton University) with the goals which can be shortly described in three main points to provide infrastructure for planetary scale experiments with networking services to provide platform for new novel services with real users to catalyze the evolution of the Internet to new service-oriented architecture

8. App - BApp - AApp - DApp - C

9. Services/Applications and Node/Slice in Virtual Lab N4N4 N2N2 N3N3 N7N7 N8N8 N1 N9N9 N5N5 N6N6 On each node can run more users (slices) Each of them is running in own virtual system One user can run more applications App1 App2 App3 SLICE Node

10. Not only PlanetLab but also other applications as Skype, Napster, GNet,… The layers have own addresses for objects, own routing App. Layer 1 a e c f b d g h App. Layer 3 jn@.cvut.cz jiri@cesnet.cz ed@rice.edu tom@stanford.edu marie@volny.cz axel@cern.ch 71721e App. Layer 2 p1 p2 p100 p111 p999... App. Layer 99 11e0fe abe0fe 11e0fe f11e00 2122fe 11e0fe c1e0fe 41e2f0 81e0fe a1e0fe bbe0fe

11. From: David Alderson CALTECH, NSF Find meeting, Dec. 2005

12. from RN with KEY: 65a1fc key d13da3 d462ba d4213f d467c4 PASTRY (DHT) function Lookup (key) d471f1 Forwarding to dxxxxx Forwarding to d4xxxx Range of local keys (c2d1 – 32aaff) d46a1c Local Range..67c5 to..71f1 Not forwarding ! RNode Hash Table keyindex value $pdata= $persons{“joe”} RNode 1 joe 88,180, $8880 121 jiri 92,168, $3900 2 2 24 -1 = 16 mil. objects Lookup (d46a1c) 82,181, $1900 tom 991 80,180, $8900 jerry 992 1 65a1fc 128.128.22.11 121 1faab1 148.33.244.1 2 192.161.1.12 dabcf0 990 192.161.1.12 dabcf1 991 192.12.12.121 dabcf2 992 $key=“dabcf2” $ip = $address {$key} keyindex ip In Pastry max key=ffff ffff ffff ffff c2d0 32ab00 0 How to address objects

13. SOA Service-Oriented Architecture IP layer (path capacity) App. Layer Application L a y e r INFRASTRUCTURE b B c a A C

14. AS SOA Service-Oriented Architecture IP layer Layer 3 Reality is determined by BGP AS 332 AS 111 AS 112 AS 333 AS 6732 a1e0fe Application L a y e r INFRASTRUCTURE b c a B A C

15. AS Router with different routing strategy for different applications CRS-1 or GPBS or ? or several virtual routers in one HW Rx IP layer B A

17. AS IP layer Rx

18. Convergence of ENGINE and PlaneLab

19. ENGINE Potential PoPs and Links DE UK FR CZ CH DK ES PL UKERNA CESNET PSNC DFN SWITCH & CERN NORDUnet SUnet RedIRIS RENATER Cisco CRS-1 router Open-source router 40G wave 10GE wave 1GE link Wave or link on GEANT2 fiber Wave or link on cross-border fiber Wave or link as managed service Wave or link on country NRENs Wave or link color codes: NLR

20. ENGINE (two sides of testbed) ENGINE scientific Network engineering

21. The ENGINE and NREN integration (connections, VLAN, users, etc.) DE CH PL CESNET backbone UNI-1 UNI-2 CZ User’s machines workstations Users resources Green – part of ENGINE testbed vlan direct via workstation u1u2 u3u4 u5 w3 w1 w2 u6 VR GN2 ENGINE testbed NREN

22. ENGINE users (connections, VLAN, etc.) DE CH PL CZ User’s machines workstations Users resources NREN infrastructure Virtual part of ENGINE testbed u5 w3 u1 u2 u4 u1, u2, w3 directly on ENGINE-VLAN u4,u5 via w3 VR ENGINE testbed

23. ENGINE virtual environment (connections, VLAN, vAS, IPaddresses, etc.) CZ u5 w3 u1 u2 u4 u1, u2, w3 directly on ENGINE-VLAN u4,u5 via w3 VR User’s machines workstations Users resources Green – part of ENGINE testbed vAS1vAS2 vAS3 IP range NREN-CZ VR client | peer with special service client | peer

24. ENGINE users and applications DE CH PL CZ u5 u21 u2 u4 u1, u2.u21,u22 directly on ENGINE-VLAN Ingres WS connection via u4,u6,u7,… LAN or internet NREN Ingres WS2 Ingres WS4 Ingres WS1 u6 u34 u7 u11 u22 Ingres WS3 u35 u44 u33 u43 u1 VR u3 Cheap and flexible infrastructure for many scientific users and different network applications VR

25. DE CH PL CZ u5 u21 u2 u4 u1, u2.u21,u22 directly on ENGINE-VLAN Ingres WS connection via u4,u6,u7,… LAN or internet NREN Ingres WS2 Ingres WS4 Ingres WS1 u6 u34 u7 u11 u22 Ingres WS3 u35 u44 u33 u43 u1 VR PLbws u3 PLbws ENGINE users and applications Cheap and flexible infrastructure for many scientific users and wide spectrum of network applications

26. What type of users and applications can utilize this architecture ? NREN itself ? YES for Network engineering ordinary Internet users ? Why ? Researchers and research teams ? Yes but who is ready ? (HW, SW, people) Modern network applications Yes, they are ready in PlanetLab !

27. PlanetLab in frame of GREN (Global Research and Educational Networks)

28. Existing tools and network applications can be re-implemented or extended into new architecture ! Peer-to-Peer Systems (DHT Distributed Hash Table) CAN, Chord, Pastry, Tapestry (building routing tables adaptively, automatic reconfiguring, using effective algorithms) Systems using effectively whole available infrastructure CDN – Content Distributed Network Replication and other systems based on “Behive” principles with O(1) lookup, Load peak multiplexing

31. http://coblitz.codeen.org:3125/http://ephyra.cvut.cz/links/tmp/FLOWS/CVUT/RAW/rawflow.02-15-2006.5

32. In internet all peers are connected (logical full mesh) Can users utilize all infrastructure effectively?

33. BitTorrent Seed node Seed node distribute file into all other nodes in the network with active engage of all nodes and segments

35. ENGINE (NE - second side of testbed) ENGINE scientific Network engineering

36. (Heavy Commercial solution) TOO STATIC

37. Fully meshed backbone with service shared virtual or optical paths Simple routing Load balancing Fast level of resilience Easy Plug-in Similar to the idea in the project “Millions Node access Network” H. Zhang et all in http://100x100network.org Simple virtual solution ENGINE future NGI backbone ? NRENs

38. From: GENI backbone working group,

39. Thank You for your attention

40. Questions ?