Version 20 (modified by, 8 years ago) (diff)


GUSH Evaluation

GENI User Shell (GUSH) provides an execution management system that allows users to describe an experiment that the GUSH tool uses to locate, and prepare resources. The GUSH software can be checked out from the GUSH SVN Repository using username guest and password is provided out of band. This GUSH evaluation started with the existing check out of the tools and updated to Software revision 159. Nebula testing required an update to revision 160.

Evaluation Time Frame: September 21, 2011 through the end of October 2011.

Gush Findings

Attempts to get sliver details for rspec 0.2 version failed, this was addressed by making changes to the gush parsing, waiting on feature check into repository.

Attempts to start the Nebula client failed with a java exception, which turned out to be missing files that were added in svn version 160.

Gush How-to

Using and existing GUSH install at revision 142 updated to the latest revision 159:

 $ cd gush/trunk; svn update
 $ make clean
 (cd api && make clean)
 make[1]: Entering directory `/home/lnevers/gush/trunk/api'
 rm -f *.o libgushapi.a api-test
 make[1]: Leaving directory `/home/lnevers/gush/trunk/api'
 rm -f gush client gush-source.tar gush-bin.tar *.o \
        terminal_parser.c terminal_parser.h terminal_lexer.c terminal_lexer.log
 $ make all
 <<< lots of output deleted>>

Gush configuration The configuration for each aggregate is manual and there is some naming inconsistencies which can cause problems. Following is a table which maps the directory.xml setting to the omni settings for each supported aggregate:

User can now start the GUSH application by selecting Gush=>Start Gush

Aggregate Name (directory.xml) resource_manager type (omni_config) aggregate type ( framework (-f)( AGGREGATE_URL (-a)
PlanetLab "geni-plc" sfa plc
Emulab "geni-pg" pg pg

Coordinating these across configurations and commands is important to get gush working.

First evaluated PlanetLab features. Using the following configuration files:


<?xml version="1.0" encoding="UTF-8"?>
    <resource_manager type="geni-plc">
      <port_map slice="bbn_gusheval" port="61414"/>


users = lnevers


urn =

Started the gush tool:

 $ ./gush -P 15555
 gush> Gush has learned about the slice bbn_gusheval.

Second, evaluate the ProtoGENI feature and using this omn_config:

<?xml version="1.0" encoding="UTF-8"?>
  <resource_manager type="geni-pg">
     <port_map slice="lnevers02" port="61600"/>

and this directory.xml:

users = lnevers

urn =

ch =
sa =
cert = ~/.ssl/protogeni/encrypted-cleartext.pem
key = ~/.ssl/protogeni/encrypted-cleartext.pem

was able to connect to each of the hosts in the slice:

$ ./gush -P 15555
gush> Gush has learned about the slice lnevers02.
Updated information on the slice lnevers02 is available.
gush> connect
Connecting to host
gush> connect
Connecting to host
gush> info mesh
Mesh: bootstrapping; (fds=-1,-1 last_heard=0) bootstrapping; (fds=-1,-1 last_heard=0)
Summary: 0 mesh members; 2 nodes connecting.

Attempts to start the Nebula client initially failed with a java exception, which was due to missing file, an updated to revision 160 resolved this issue. The Nebula client is invoked as follows:

$ cd nebula
$ sh ./run

User must define the location of the gush software by choosing Edit=>Preferences, the preferences dialog also allows setting the location of the SSH private key:

Email us with any questions and feedback on this page!

Attachments (9)

Download all attachments as: .zip