Version 2 (modified by Jeanne Ohren, 7 years ago) (diff)


Description of Test Cases for GIMI Functionality



Compatible AMs


Compatible AMs

Experiment Scripts

Basic Ping-All Use Case

Step 1: Create GIMI slice

Pre-conditions: None

Using one of the Rspecs listed above, create a slice using omni or the GENI portal and add resources at one of the compatible aggregate managers.

Expected Result:

  1. A sliver with the following topology is created at one of the aggregate managers.

<insert image here>

  1. All nodes are in a ready state.
  2. OMF RC is running on each node and /var/log/omf_rc.log shows entries similar to this:
        insert log messages here

Step 2: Log in to Labwiki


  • You have an account at an InCommon institution or the GENI IdP
  • You are a member of at least one project in the GENI CH.

Go to the URL and log in with a GENI Portal user account.

Expected Result:

You are successfully logged in to Labwiki and your name appears in the upper right corner of the page.

Step 3: Create an Experiment Context


You are logged in to Labwiki.

  1. Click on "Add Context" in the upper right hand corner of the Labwiki page to create a new experiment context.

  1. Select a project, enter a name for your experiment, and click on 'Save'.

Expected Result:

  • The context saves successfully.
  • The context is available in the drop-down box in the Execute pane.

Step 4: Load Experiment Script


You are logged in to Labwiki.

A. Load an existing experiment script

  1. Place cursor in the search box of the Prepare pane and start typing the name of the existing script.


  1. Select the step1_pingall script from the narrowed-down list of scripts.

B. Create and save a new experiment script

  1. Click on the plus (+) sign in the Prepare page.
  2. Select "Ruby" from the drop-down box, enter a filename, and click on "Create"
  3. Enter the new filename into the Search box and select the script from the list of scripts.
  4. Enter the experiment script contents (see step1_pingall in Experiment Scripts above) and click on the Save icon.

Expected Result:

The step1_pingall script has been loaded into the Prepare window, edited as needed, and saved.

Step 5: Execute Experiment Script

Pre-conditions: The step1_pingall experiment script has been loaded into the Prepare window, edited as needed, and saved.

Expected Result:

A. Drag script from Prepare to Execute panel

  1. Drag the step1_pingall script's icon from the Prepare pane to the Execute pane and drop in the Execute pane.

B. Fill out the form

  1. Enter a name for the experiment in the Name: box.
  2. Select the project in which you created your slice from the Project drop-down.
  3. Select the context you created from the Experiment drop-down.
  4. Select your slice from the Slice drop-down.
  5. Make sure the values in the source1-source5 boxes match the node names in your slice.

C. Start experiment

  1. Click on the 'Start Experiment' button.

Expected Result:

  1. You see entries in the
  2. You see a graph similar to this one:

Step 6: Dump Results to iRODS


Your step1-ping_all experiment has completed successfully. You have created an iRODS account via the GENI Portal.

  1. Click on the 'Dump' button at the top of the Execute pane.
  2. Log in to and enter the following:
  3. Traverse to /geniRenci/home/gimiadmin/<project>/<context>/... to find the data that was dumped.

Expected Result:

  • An SQL file has been placed at the location /geniRenci/home/gimiadmin/<project>/<context>

Long-lived Experiment Use Case