PlanetLab Future Directions

1
PlanetLabFuture Directions

• Marc E. Fiuczynski
• Princeton University
• PlanetLab Consortium

2
Future Directions Overview

• Federation
• VINI (layer 3 data/control plane research)
• PlanetLab GOLD
• PlanetLab for Developing Nations
• Management Monitoring

3
PlanetLab Facility Today

• 784 servers at over 382 sites
• Co-located throughout the (developed) world _at_
  Uni. Companies
• Co-located at network crossroads (Internet2, RNP,
  CERNET, )

4
PlanetLab Growth 07
Russia
More Brazilian Universities?! Latin America
(RedClara)
Japan (JGN2)
5
Other PlanetLab based Testbeds

• PlanetLab EU PlanetLab JP
• Federated with PlanetLab
• EverLab
• private PlanetLab for HPC and Networking
  researchers(EU Israel)
• OneLab Intels Wireless PlanetLab
• PlanetLab for wireless research (France)
• VINI
• PlanetLab for layer 3 research

6
Federation

• Continue to evolve evaluate federation
  implementations
• Develop tools to express enforce peering
  agreements
• Deploy additional Management Slice Authorities
• Integrate GENI primitives into PlanetLab
• Node API to manage slices
• Name space for slices and nodes

7
Integrate GENI primitives

• Name space standardization
• PlanetLab approach
• slice names princeton_codeen
• node names DNS hostnames
• GENI approach
• Assumes a top-level naming authority
• Top_level_authority.sub_authority.sub_authority.na
  me
• slice names geni.us.planetlab.princeton.codeen
• node names geni.us.backbone.nyc.node1
• Human readable names are bound to GGIDs
• GGIDs UUID public key

8
VINI PlanetLab for layer 3 research

• VINI is a
• Software base (downstream from PlanetLab)
• New kernel to support improved network
  virtualization
• Tools to instantiate virtual topologies
• Private PlanetLab with its own nodes separate

9
VINI Collaboration Opportunities

• Support opportunities to improve performance
• Stanfords NetFPGA
• Washington Universitys BladeServer
• Deploy interconnect with additional VINI
  instances
• E.g., japan, europe, latin america,

10
PlanetLab GOLD

• Extend myPLC nodes to support reservations and
  cost recovery
• Deploy additional nodes / bandwidth, as
  appropriate
• Develop model to permit pilot demonstrations

11
PlanetLab Story (to date)
Goal Seamless conception-to-deployment process
Deployment
Analysis
Simulation / Emulation
Experiment At Scale
(models)
(code)
(results)
(measurements)
12
Deployment Gap
Commercial Deployment
Pilot Demonstration
Ideas
Maturity
Deployment Study (PlanetLab)
Controlled Experiment (EmuLab)
Analysis (MatLab)
Time
13
Motivation

• Research
• peering, market-based resource allocation
• new customer requirements
• Education
• student exposure to economic concerns
• example pilots (e.g., University Channel)
• Industry/Academia Interaction
• foster collaboration
• accelerate tech transfer

14
Example Pilots

• University Channel
• Wikipedia
• Citeseer
• OLPC
• World Bank
• Polish Telecom (FT, BT, ATT)
• Pay-on-Demand Content Distribution

15
PlanetLab for Developing Nations

• Support disconnected nodes
• Support system management at scale
• 100K nodes per myPLC
• Pursue pilot deployments in Latin America,
  Africa, etc.

16
Management Monitoring

• Enhance automate node management / monitoring
• Node health in three dimensions
• Time (history)
• External observation (from different vantage
  points)
• Internal observation (cpu utilization, storage
  availability, dns/ntp/etc. availabilitylatency)
• Develop ML-based anomaly detection for node

17
Future Directions Overview

• Federation
• VINI (layer 3 data/control plane research)
• PlanetLab GOLD
• PlanetLab for Developing Nations
• Management Monitoring