Upload
gary-ramsey
View
215
Download
1
Tags:
Embed Size (px)
Citation preview
PlanetLab Europe 2008
Thomas Bourgeau
Laboratoire LIP6 – CNRSUniversité Pierre et Marie Curie – Paris 6
http://www.lip6.fr/rp
3
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
10
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
12
PlanetLab Europe Goals
• Extend
– Extend PlanetLab into new environments, beyond the traditional wired internet.
• Deepen
– Deepen PlanetLab’s monitoring capabilities.
• Federate
– Provide a European administration for PlanetLab nodes in Europe.
14
PlanetLab Europe Terminology
• 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
15
PlanetLab Europe Roles
• Principal Investigator (PI): The PIs at each site are responsible for managing slices and users at each site. PIs are legally responsible for the behavior 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.
16
Federation•Set up a functional PlanetLab Central in Europe to manage European sites
•Create a federation between PlanetLab Europe and PlanetLab Central at Princeton
• 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.
20
PlanetLab Today
- A set of end-hosts
- A limited view of the underlying network
- Built on the wired internet
21
PlanetLab Europe Vision
- Reveal the underlying network
- Extend into new wired and wireless environments
22
PlanetLab Europe Emulation component
• 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.
23
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.
24
PlanetLab Europe Emulation component
• Configuration of the DBox:– Add sliver/nodes on a Dbox with the
DummyNet API methods located on PLE.
AddDbox
25
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
26
PlanetLab Europe Emulation component
• Dbox experiment using hping:– The user can use the hping application on
his sliver through an ssh connection.
ssh
27
PlanetLab Europe Emulation component
• DBox monitoring :– The Dbox continuously monitor the traffic
flowing through the interface and report on web page dynamically.
28
PlanetLab Europe Wireless component
• Help service providers to test their applications within the wireless mesh network.
• Integration of Madwifi drivers:– ease of use – compatibility
29
PlanetLab Europe Wireless component
• 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
30
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
31
PlanetLab Europe Wireless component
• If no Gateway is configured the user can: – Access to each nodes of the wireless multi-hop mesh
network with his ssh key.
– Use the configured wireless command.
– Launch application (Streaming video, iperf, hping, …).
ssh
32
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
36
Sites behaviour with CoTop
• 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 site is down, but using others' resources(Red)
– Down: site is down, but no usage
37
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.
38
PlanetLab Europe Site creation
•How to join?– Just connect to– https://planet-lab.eu– Fill in the “site registration”
form
39
PlanetLab Europe Site creation
• Warning: there are fields that should be unique across all federated PLC
– Login_base mustmust be unique!!
40
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.
42
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.