Bogus PI signups were the main problem this week, but users should not be able to sign up as a PI now. Also maybe we don't want to ask people to respond to pl_mom messages as this spawns a lot of support tickets.
Explaining the whitelisting feature of the current API was bothersome.
Mike and Andy were not aware that they were on support duty so David carried the load himself. Possibly someone should write a script to inform those on support each week that they're up.
PlanetLab Operations is developing a new tool, called Site Assistant, to help sites keep their nodes running and connected to PlanetLab. In addition, we will begin running a program called Monitor to notify a Site's Technical Contact and PI about observed problems with registered PlanetLab machines. The set of machines affected will be increased gradually. For additional details on when your machines will be affected, please see the Deployment Schedule. As well, for details on the policy that Monitor implements to encourage continued site participation, please see Monitor Policy.
Step-by-step instructions to deploying a "Hello World" application on PlanetLab Hello World Tutorial
An older version is also available in pdf form (PDF).
| Aug 17||Tony|
| Aug 24||Andy|
| Aug 31||Marc|
| Sep 6||Faiyaz|
| Sep 13||Tony|
| Sep 20||Andy|
| Sep 27||Tony|
| Oct 5||Andy|
| Oct 12||Tony|
| Oct 19||Andy|
| Oct 26||Sapan|
| Nov 2
PlanetLab (http://www.planet-lab.org/) is a distributed systems research test bed. We manage 1000+ machines world wide. These machines may share access to both research, local and public Internet. These services are actively managed by researchers granted access to PlanetLab accounts. And, we enforce a project Acceptable Use Policy (AUP) https://www.planet-lab.org/aup that should direct the behavior of researchers running experiments within PlanetLab.
Upgrade VINI using latest MyPLC 9-21-2007
Vini's MyPLC has been upgrade. This means that:
1) DB schema was converted and all existing data imported
2) API code was updated.
3) Web gui was already using drupal. Kept intack.
I will continue to keep the VINI backend (db/api) in sync PLC.
Added new api method GetSliceKeys(). This methods returns an array of structs containing public key info for users in the specified slices. If slice_filter is specified and is an array of slice identifiers or slice names, or a struct of slice attributes, only slices matching the filter will be returned. If return_fields is specified, only the specified details will be returned.
Users may only query slices of which they are members. PIs may query any of the slices at their sites. Admins and nodes may query any slice. If a slice that cannot be queried is specified in slice_filter, details about that slice will not be returned.
- PlanetLab: Catalyzing Network Innovation. October 2007. [ppt slides].
- PlanetLab: Evolution vs Intelligent Design in Global Network Infrastructure. Updated May 2007. [ppt slides].
- PlanetLab: A Strategy for Continually Reinventing the Internet. Presentation at OSTP. [ppt slides].
- PlanetLab: Evolution vs Intelligent Design in Global Network Infrastructure. Keynote Speech at Usenix 2006. [ppt slides].
- Presentations from the May 11th 2006 "private PlanetLab" meeting:
- Architectural Questions, Larry Peterson. [ppt slides].
- Workshop Discussion, Andy Bavier. [ppt slides].
- Presentations from the May 1st 2005 PlanetLab Users Meeting:
- PlanetLab: A Blueprint for Introducing Disruptive Technology into the Internet, Scott Karlin, Presented at the 17th Asia-Pacific Advanced Network (APAN) Meeting, University of Hawaii, January 2004. [pdf slides].
- PlanetLab: A Blueprint for Introducing Disruptive Technology into the Internet, Larry Peterson, Presented HP and DoCoMo Labs, January 2004. [pdf slides].
- An Overview of the PlanetLab Architecture, Scott Karlin, Presented at the Winter 2004 Joint Techs Workshop, University of Hawaii, January 2004. [pdf slides].
- PlanetLab: A Blueprint for Introducing Disruptive Technology into the Internet, Scott Karlin, Presented at the joint Princeton ACM / IEEE Computer Society meeting, November 2003. [pdf slides].
- What are people doing in/on/with/around PlanetLab?, Timothy Roscoe, April 2003. [ppt slides], [pdf slides].
- PlanetLab: an open community testbed for Planetary-Scale Services, Timothy Roscoe, April 2003. [pdf slides].
- PlanetLab: A Blueprint for Introducing Disruptive Technology into the Internet, Larry Peterson, December 2002. [ppt slides].
- PlanetLab: a foundation on which the next Internet can emerge, Timothy Roscoe, September 2002. [ppt slides], [pdf slides].
- PlanetLab: a Petri dish for the next Internet, Timothy Roscoe, July 2002. [ppt slides], [pdf slides].
- Towards a Distributed Test-Lab for Planetary-Scale Services, Timothy Roscoe, June 2002. [ppt slides], [pdf slides].
- PlanetLab: A Distributed Test Lab for Planetary Scale Network Services, Timothy Roscoe, June 2002. [ppt slides], [pdf slides].
- Towards a Distributed Test-Lab for Planetary-Scale Services, David Culler, June 2002. [ppt slides], [pdf slides].
The status of PlanetLab is reported by several programs and tools that view different aspects of the nodes and their connectivity. The following is a list of some of the current status views of PlanetLab. Additional (non-functional) links are listed in the next section below.
This page contains links to a list of "slice management tools" contributed by the PlanetLab user community. PlanetLab users are strongly encouraged to make use of these tools to manage their slices.
Plush from University of California, San Diego. Users describe experiments or computation in XML, and Plush uses it to locate, contact, and prepare resources. It includes a Nebula GUI that allows users to build, visualize and run their applications without using the command-line interface.
Updated: May 2, 2007
To accommodate ongoing development efforts, SVN is broken down in the following ways, for each module (application, library, script, etc, that is each compiled into a single package):
- trunk : Initial checkins of code. This code may be broken and probably requires further development.
- branches: Code ready for production. This code is stable, but may need more testing. Patches are first applied to head, then merged (selectively) into this branch. This can leave head as a free for all, but allows the developer to move valuable code upstream by hand. It doesnt have to be a direct copy of head.
- tags: Incremental tag of the branch. Its a snapshot of a point in time that encompasses all changes made to the branch at that date. It's primarily used to give to other people not on the development team. This code is very stable, production quality, and is never altered. Rather, for each addition, a new tag is made.
SVN directly translates to nodes in the following manner: