Connect to PlanetLab network
Setup an overlay
To insert key/value pairs, to check the routing table, relay list, bandwidth, or
cpu utilization of a node, we provide an executable called 'checker'.
Node's cpu, bw & routing table:
checker -R -a planetlab01.erin.utoronto.ca -p 7080
Node's cpu, bw & resource table:
checker -O -a planetlab01.erin.utoronto.ca -p 7080
Node's turn allocations:
checker -N -a planetlab01.erin.utoronto.ca -p 7080
Node's relay list: checker -E -a planetlab01.erin.utoronto.ca -p 7080
Insert key/value: checker -i salmanbaset -v value -a planet1.l3s.uni-hannover.de -p 7080
LookupObject: checker -o salmanbaset -a planet1.l3s.uni-hannover.de -p 7080
LookupUser: checker -u xQygPShB -a planet1.l3s.uni-hannover.de -p 7080
We are running an overlay of 1000+ nodes on the Planet Lab. Each node has a
corresponding USERID. The USERIDS and hostnames of nodes can be found here.
So how do we check that our overlay is working correctly? How much traffic is
being routed through a node? We provide an executable called checker that can
be used to acquire a node's routing table, resource table and its bandwidth
consumption. Using this executable, we use two mechanisms to check the
consistency of the overlay:
Check the state of all nodes. There should be as many USERIDs in the overlay as
the number of nodes.
Perform 1000*1000 lookups for USERIDS, i.e., from each node we lookup the USERID
of 1000 nodes. Takes time!