Login
[planetlab logo] An open platform for developing, deploying, and accessing planetary-scale services

Community
Joining
News
Documentation
Software

End-User Services

Several end-user services run continuously on PlanetLab, generating over 2TB of live network traffic and contacting over 1M unique IP addresses every day. Users at PlanetLab sites (and elsewhere) are encouraged to take advantage of these services.

Content Distribution Networks

service MB/day destination IPs/day
CoralCDN 1,845,558 716,683
CoDeeN 351,008 136,252
Cobweb 46,248 42,763

Distributed Hash Table

service MB/day destination IPs/day
OpenDHT 40,455 671

Scalable Large-File Transfer

service MB/day destination IPs/day
CoBlitz 169,188 136,252
Loci currently inactive

Robust DNS Resolution

service MB/day destination IPs/day
CoDNS 351,008 136,252
CoDoNS 2,322 0

Routing Overlays

service MB/day destination IPs/day
Internet Indirection Infrastructure (i3) 89,085 206

Multicast

service MB/day destination IPs/day
ESM currently inactive
TMesh currently inactive

Email

service MB/day destination IPs/day
ePOST 1,630 128.00

Publish-Subscribe News Access

service MB/day destination IPs/day
CorONA 3,532 0

Mobile Access

service MB/day destination IPs/day
DHARMA 169 171

Network Measurement & Observation

Many researchers use PlanetLab as an observation Platform from which they can measure and map the Internet, detect anomalies, and diagnose failures. Few of the tools developed to support this activity are available as continuously running PlanetLab services. The main exception is ScriptRoute, which allows users to execute measurement scripts from PlanetLab's man vantage points.


Infrastructure Services

PlanetLab service developers commonly take advantage of ''helper'' services, commonly called infrastructure services, to deploy, monitor, and maintain their services and experiments. New PlanetLab users are strongly encouraged to leverage these services, rather than reinvent the wheel.

Brokerage Services

These services are used to acquire additional resources, for example, to run an experiment or demo during periods of heavy load.

Environment Services

These services are used to distribute software packages, resolve dependencies, and remotely control a slice. Users should be aware that there are many similar tools available; see the Wiki for more examples. We call these two out because the combination seems to be getting the most traction in the community. It would be a great service to the PlanetLab community for someone to write a ''best practices'' document that helps new users figure out what combination of deployment and management tools to use for their slice.

Monitoring & Discovery Services

These are related services that can either be used to monitor the behavior running nodes or slices, or to help users discover what resources are available on what nodes.

service MB/day destination IPs/day
SWORD currently inactive
CoMon 3,974 512
PsEPR 13 244
Ganglia currently inactive
IrisLog currently inactive
PlanetFlow N/A N/A

Recent Contributions

An experimental Wiki page has been created. The Wiki allows users to post information about new services, and so it may have more up-to-date information than this page. A similar page exists for contributed software and tools.