1. October 27 th 2005Thierry Parmentelat - INRIA The OneLab project Thierry Parmentelat - INRIA

2. October 27 th 2005Thierry Parmentelat - INRIA A first (missed) attempt EU_planetlab was filed in spring within the SSA (Specific Support Action) framework not funded –ranked 2 nd though too much focused on PL operations not innovative enough too much academic

3. October 27 th 2005Thierry Parmentelat - INRIA OneLab : a renewed attempt Within the STREP framework Specific Targeted REsearch Project Filed on September 21 st 11-parties consortium Academic  UPMC, INRIA, U’s : Madrid, Louvain, Napoli, Pisa Industrial  Intel Research Cambridge, Ericsson Hungary, France Telecom, Alcatel Italia, Telekomunikacja Polska Decision expected in 2-3 weeks

4. October 27 th 2005Thierry Parmentelat - INRIA Orientation revisited More balanced between Operations (PLE) Innovation (add new features) Discussions between Experimental platforms vs Simulation And between Realistic vs Deterministic

5. October 27 th 2005Thierry Parmentelat - INRIA So you want to setup an experimental testbed Creating one’s local testbed Maximal flexibility Costly and time-consuming (admin & user) Reaching real-scale requires agreements with – potentially many- other labs Tempting to elaborate on PlanetLab (partly) representative of the Internet, geographically scattered, wide impact in the community, still growing, cost-effective, very low-administration, unique management UI.

6. October 27 th 2005Thierry Parmentelat - INRIA What’s missing? PlanetLab still lacks a few features: poor support for wireless no/poor mobility control on the environment not deterministic (lacking framework for gathering measurements)

7. October 27 th 2005Thierry Parmentelat - INRIA Reproduce wireless links? Can be done for “stable” connectivity networks (UMTS/WiMax) Difficult for unstable connectivity (ad- hoc) Identify controllable aspects and define necessary extensions to attach such networks Or identify configurable parameters and run experiments with an “emulated” wireless network

8. October 27 th 2005Thierry Parmentelat - INRIA OneLab’s Objectives (2) Operations setup and run PLE a means to acquire autonomy would start with 20-30 hosts more if possible, no commitment newcomers welcome older nodes: how seamless is a move

9. October 27 th 2005Thierry Parmentelat - INRIA OneLab’s Objectives (3) New capabilities in nodes Native wireless support  WiFi - ad hoc networks  WiMax  UMTS More mobility  Multihomed connections – ipv6  Deal with unstable connectivity

10. October 27 th 2005Thierry Parmentelat - INRIA OneLab’s Objectives (4) Integrate/mix emulation tools Comes in handy for hard-to-support types of links, such as ad hoc networks Apply to dummynet Active & passive measurements Locate spots to perform measurements Design an API to expose measurement results Apply to CoMo

11. October 27 th 2005Thierry Parmentelat - INRIA Does this fit into PL / open questions More complexity in the ‘delivered’ software & basic configuration environment info more complex Breaks the ‘uniform’ model host configuration more tricky control mechanisms needed  tune wireless attributes  drop interface in multihomed  reservation ? incentives for deploying new features where the private PL comes in

12. October 27 th 2005Thierry Parmentelat - INRIA Beyond OneLab Several possible scopes The public PlanetLab Private PL Consortium-wide PL Reservation-based (GRID) “PlanetLab EveryWhere” “IP on everything” Public PL p Multi - party p p p p p

13. October 27 th 2005Thierry Parmentelat - INRIA Private PL’s Setup of a toy local PL Also handy for one-2-one agreements Planning to move to FC4 Intended to deploy wider Implementing moving topologies, e.g. ‘clouded’ routers Lacked the flexibility at the time Also many idle machines could be involved

14. October 27 th 2005Thierry Parmentelat - INRIA OneLab-Private PlanetLab Setup OneLab-”Private” PlanetLab for integrating new components Public = PLE Private = OneLab WP5 New stuff (wireless,mobility)

15. October 27 th 2005Thierry Parmentelat - INRIA Managing complexity PLE + OneLab + 2 local PLs = 4 PLs Differents constraints Still, 4 servers is a lot Ability to easily switch between PLs applicable to migration of nodes from PLC -> PLE afap : plnode.txt or CD – not both Can we still improve this ? One single server (DB+rpm repo) Serving several ‘domains’ no change at all on the node side 1node -> 2 domains ?

16. October 27 th 2005Thierry Parmentelat - INRIA Conclusion Engineering issues No IP-address, ipv6 Customize ‘delivered’ software Plnode.txt / CD simplified Open questions Take into account node diversity How to implement controls Interaction owner/SA (reservation) Create momentum on new technologies

17. October 27 th 2005Thierry Parmentelat - INRIA Conclusion - ctd Federation become active players Private PL valuable as such leverage dissemination flexibility Virtualization : effective HW management idle nodes many logical PLs