wiki:GushProto

Version 47 (modified by Vic Thomas, 14 years ago) (diff)

--

Project Number

1621

Project Title

GENI Experiment Control Using Gush
a.k.a. GushProto, GUSH

Technical Contacts

PI: Jeannie Albrecht jeannie@cs.williams.edu / +1 413 597 4251
Amin Vahdat vahdat@cs.ucsd.edu / +1 858 534 4614

gush-summer-students

Jeannie Albrecht working on Gush with undergraduates Danny Huang and Kelsey Levine at Williams College.

Participating Organizations

Williams College http://www.williams.edu, Williamstown, MA
UC San Diego http://www.ucsd.edu, San Diego, CA

Scope

The scope of work on this project is to design and implement a prototype to build Gush (the GENI User Shell), a robust experiment control and management framework for GENI. The final product of this work is expected to be a fully functional framework that supports experiment control through three user interfaces, including a graphical user interface (GUI), command line interface, and a programmatic interface.

This work will include design of an API in Gush for interacting with GENI Clearinghouses. Gush will integrate with GENI Clearinghouse prototypes provided by the control framework developers to test the Gush API and the use of slice interaction functions. Initial work will be with the PlanetLab control framework using XML-RPC communication with the PlanetLab Central Database (PLC). Development will focus on getting the Gush command line and programmatic interfaces working before moving on to the graphical interface, with an emphasis on detailed error reporting that will simplify debugging.

Gush Architecture Picture (from http://gush.cs.williams.edu/trac/gush/attachment/wiki/AboutGush/gush-arch.png)

Current Capabilities

Gush can seamlessly run experiments using PlanetLab, GpENI, and Emulab resources. Prof. Albrecht (PI) plans to have students run experiments on PlanetLab in her Distributed Systems class this semester, and release the code publicly within the next few months.

Raven/Stork has been integrated into Gush. All of the new Gush code has been committed to there svn repository and there is a new example on the Wiki page (http://gush.cs.williams.edu) that explains how to use Stork/Raven to install software in Gush.

Milestones

MilestoneDate(GUSH: S2.a prototype 0.2)?
MilestoneDate(GUSH: S2.b Course development)?
MilestoneDate(GUSH: S2.c Raven integration)?
MilestoneDate(GUSH: S2.d GUI 0.1)?
MilestoneDate(GUSH: S2.e support two control frameworks)?
MilestoneDate(GUSH: S2.f spiral 2 id mgmt)?
MilestoneDate(GUSH: S2.g 0.3 release)?

Project Technical Documents

Gush User Study 1
Gush User Study 2

Gush based course work available from PI upon request.

Website maintained by Williams College: Gush

Software

To check out Gush code out of SVN use "svn co http://gush.cs.williams.edu/svn/gush/trunk --username guest". Please contact jeannie AT cs DOT williams DOT edu for the password.

Quarterly Status Reports

4Q08 Report
1Q09 Report
2Q09 Report
3Q09 Report
4Q09 Report

Spiral 1 Connectivity

PlanetLab control framework.

For Spiral 1, Gush will be deployed to GENI PlanetLab nodes. Experimenters will download the Gush controller to their workstation from the Gush project website. Gush automatically downloads the client software to the PlanetLab machines in use. There is no GENI requirement for UCSD/Williams connectivity.

IP Connectivity: IP connectivity required from GUSH controller (typically user desktops) to PlanetLab machines in slice. IP connectivity required between controller and PlanetLab clearinghouse. IP connectivity required between PlanetLab nodes in experimenter's slice and Gush code repository to download so Gush software if machines don't already have Gush client installed.

Layer 2 Connectivity: Gush does not require any layer 2 virtual ethernets.

GEC Presentations

GEC 2 Presentation
GEC 3 Presentation
GEC 4 Presentation
GEC 5 Presentation

GPO Liaison System Engineer

Vic Thomas

Related Projects

ProvisioningService

PlanetLab

Attachments (18)