OneLab OneLab An Open Federated An Open Federated Laboratory to evaluate Laboratory to evaluate the possible futures of the possible futures of the Internet 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
85
Embed
OneLab An Open Federated Laboratory to evaluate the possible futures of the Internet
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. - PowerPoint PPT Presentation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
OneLabOneLabAn Open Federated Laboratory An Open Federated Laboratory
to evaluate the possible to evaluate the possible futures of the Internetfutures of the Internet
Serge Fdidahttp://www-rp.lip6.fr/~sf/
Université Pierre et Marie Curie – Paris 6
Laboratoire LIP6 – CNRS
France
SBRC 2008, May 29, Rio de Janeiro
Remaining grand challenges in networking:
Are there any?
Short answer!
Pick one :
YES
NO
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…
9
10
The Polymorphic Internet : Some Internet Future(s)
•The Network is a Database
•The (Access) Network is The (Access) Network is WirelessWireless
•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
Welcome to PlanetLab Europehttps://www.planet-lab.eu
55
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
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
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
PlanetLab Europe Wireless component
• If no Gateway is configured the user can: – Access to each individual node of the wireless multi-
– 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
Federation mechanism
73
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
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
OneLab2 Organisation
WP0 Management
Pillar 1 - Platform
WP5 Packet
Tracking
WP4 Topology
Information
WP3 Dissemination
Pillar 2 - Tools
WP8 SAC
WP9 Benchmarking
WP7 Content
WP6 Wireless
Pillar 3 - Customers
WP1 Integration Contributes code
WP2 Operations
Provides monitoring tools
Provides
PlanetLab Europe
Delivers the OneLab Build
Provides monitoring tools
Contribute code
77
Outline
•PlanetLab
•OneLab
• Services, management and operation
78
Welcome to PlanetLab Europehttps://www.planet-lab.eu
79
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.
82
Joining PlanetLab Europe
83
Joining PlanetLab Europe
89
PlanetLab Europe Creates a slice
The PI at your site should validate your slice
91
PlanetLab Europe Manages your slice
92
PlanetLab Europe Node creation
94
Monitoring Node trafic with PlanetFlow
95
Monitoring Node trafic with PlanetFlow
96
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
Current situation
98
Uptime
99
Avg. CPU load
100
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)