wiki:MillionNodeGENI

Version 34 (modified by jmccolga@bbn.com, 9 years ago) (diff)

--

Project Number

1645

Project Title

A Prototype of a Million Node GENI
a.k.a. MillionNodeGENI, MILNGENI

Technical Contacts

PI Thomas Anderson (mailto:tom@cs.washington.edu / 206 543 9348)
Co-PI Justin Cappos (mailto:justinc@cs.washington.edu / 206 685 4131)

Participating Organizations

University of Washington
Paul Allen Center for Computer Science and Engineering
Box 352350
Seattle WA 98195-2350

Photo of project team.
The Million Node GENI project team

Scope

The scope of work on this project is to specify, build, and demonstrate a prototype end host deployment platform consisting of three components: a) a general-purpose yet safe execution environment for experimenter code running on end hosts, b) a light-weight, programmable and customizable proxy for end hosts for redirecting end-user traffic into GENI, and c) a clearinghouse for resources contributed by end users who have opted into the system. Specific development goals include:

  1. Development of a viable end-host virtual machine
  2. Control-plane integration, including resource discovery and reservation; experiment debug and control
  3. End-user configuration and management tools
  4. Deployment strategies such as inclusion in Bit Tyrant or web plug-in
  5. End-user policy & awareness issues and mechanisms

Diagram showing relationship between end-host VM, node manager and experiment manager.

Milestones

MilestoneDate(MILNGENI: S2.a Installer v 0.1)? Installation scripts and simple packaging for Windows / Mac / Linux.
MilestoneDate(MILNGENI: S2.b End hosts with intermitted connectivity)? Operation with end-hosts that have intermittent connectivity and/or are behind firewalls and NATs.
MilestoneDate(MILNGENI: S2.c Implement example applications)? Example applications: Seobinggo and Viewpoints.
MilestoneDate(MILNGENI: S2.d Create an example assignment)? Example assignment leveraging Seattle that an educator might use.
MilestoneDate(MILNGENI: S2.e Integrate with ProtoGENI)? Link to documentation and software
MilestoneDate(MILNGENI: S2.f Clearinghouse API spec. for end-hosts)? Specification for Clearinghouse API for end-hosts.
MilestoneDate(MILNGENI: S2.g v0.1 of end-host clearinghouse)? Reference implementation v0.1 of end-host clearinghouse.
MilestoneDate(MILNGENI: S2.h Sprial 2 identify management mechanisms)? Integrate Sprial 2 identify management mechanisms.
MilestoneDate(MILNGENI: S2.i Collaborate with O&M team)? Collaborate with O&M team on methods to share O&M data with other GENI groups.

MilestoneDate(MILNGENI: S3.a Demonstration of Million Node GENI at GEC9)?
MilestoneDate(MILNGENI: S3.b Demonstration at GEC10 and Experimenter Outreach)?
MilestoneDate(MILNGENI: S3.c MNG aggregate is operational)?
MilestoneDate(MILNGENI: S3.d Demonstration at GEC11 and Experimenter Outreach)?
MilestoneDate(MILNGENI: S3.e Documentation and code release)?

Project Technical Documents

End Host VM Design Techniques

Node Manager Design (Check https://seattle.cs.washington.edu/wiki/NodeManagerDesign for updates.)

RSpecs in the Million Node GENI system

Description of how NATed nodes connect to the testbed

Software Deliverables

The node manager and repy (end host vm) are in the seattle_repy.tgz tarball that can be downloaded from https://seattlegeni.cs.washington.edu/geni/download/flibble/. Install the node manager on the local machine by running ./install.sh. Note that you should have Python 2.5.2 installed (but it may work with Python 2.5.X or 2.6).

The reference implementation of a trivial experiment manager (a test client for the node manager) can be downloaded from http://seattlegeni.cs.washington.edu/dist/demokit.zip. This contains seash.py which is a trivial PLuSH / GUSH-like experiment manager.

The installer is available at https://seattle.cs.washington.edu/wiki/BaseInstallers.

Libraries that implement connectivity from NATed nodes at https://seattle.cs.washington.edu/browser/seattle/trunk

XML-RPC server that integrates the SeattleGENI project with the Protogeni project.: https://seattle.cs.washington.edu/wiki/ProtogeniIntegration.

Quarterly Status Reports

December 2008 Report
April 2009 Report
June 2009 Report
September 2009 Report
December 2009 Report
March 2010 Report
June 2010 Report

Spiral 1 Connectivity

Part of the ProtoGENI cluster.

Connectivity issues need to be sorted out (NAT traversal, intermittent connectivity, etc). End user devices will already have IP addresses. Need to figure out how they connect to clearinghouses, etc.

GPO Liaison System Engineer

Vic Thomas mailto:vthomas@geni.net

Related Projects

Attachments (12)