wiki:GeniExperiments

Version 11 (modified by hmussman@bbn.com, 7 years ago) (diff)

--

GENI Experiment Workflows: Overview

1) Range of GENI Experiments (Harry)

There will be a wide range of GENI experiments, with different characteristics, including these:

a) Student solves a class problem

b) Student executes an on-line tutorial, or follows a reference experiment

c) Researcher evaluates an algorithm or concept

d) Researcher evaluates the performance of a configuration

e) Researcher gathers the results of one or more experiments, and writes a paper

f) Researcher gathers the results of many experiments, and writes a thesis

g) Experimenter prototypes a service, without opt-in users

h) Experimenter prototypes a service, with opt-in users

i) Experimenter demonstrates a service to selected opt-in users

j) Experimenter offers a service to many opt-in users for a long period of time

k) Operator evaluates representative GENI slice performance, such as networking performance, to troubleshoot problems

l) Operator evaluates representative GENI slice performance, such as networking performance, over an extended period of time, and shares their data with others

2) Characteristics of GENI Experiment Workflows (Harry)

a) From a simple to a complex experiment

b) By a novice or an expert experimenter

c) From a short-term to a long-term experiment

d) Using tools with graphical or script-driven interfaces

e) Covering actual experiments, tutorials, and "reference experiments"

3) Goals for GENI Experiment Workflows (Jeanne)

a) Start with a basic GENI experiment/tutorial/test workflow that uses standardized, self-contained steps

b) Because self-contained, allows for all the variations in flow that occur in a real experiment: repeating steps (e.g., many runs); re-ordering steps (e.g., analyzing much later); skipping steps (e.g., do not archive)

c) Because standardized and self-contained, makes it easier to design tools, by being able to focus on tools for each step, and then connections (interfaces) between steps.

d) Because standardized, makes it it easier for the user to understand a tutorial, since all will follow the same outline.

e) Later, produce variations that cover additional types of experiments

4) High-level look at Basic GENI Experiment/Tutorial/Test Workflow (Jeanne)

figure

5) Steps in Basic GENI Experiment/Tutorial/Test Workflow (Harry)

a) Will start with one "Basic GENI Experiment/Tutorial/Test Workflow"

b) Will be used to guide:

  • Experiment management tool design
  • I&M tool sets
  • Contents of GENI tutorials
  • Operational tests, i.e., acceptance tests of GENI racks

c) See basic workflow steps

6) Current Mapping from Basic GENI Experiment/Tutorial Workflow to Experiment Management Tools (Jeanne)

figure

7) Towards a Standardized GENI Tutorial Format (Jeanne and Harry)

8) Example Tutorials (Jeanne and Harry)

9) Example GENI Acceptance Tests (Luisa)

10) Example Reference Experiments (Jeanne and Harry)

11) Issues

a) Can we agree on these standardized, self-contained steps? what changes or additions?

b) Issue: variations with type of users (novice to expert) and thus interfaces (graphical to script); can these be mixed?

c) Issue: variations between InstaGENI and ExoGENI, between GIMI and GEMINI; is there a common set?

d) Issue: variations from this basic workflow, to more-specialized workflows; which should be considered?

e) Next steps?

References

workflow text

related storyboard

Currently being used by GIMI and GEMINI I&M projects.

See GIMI GEC15 tutorial that follows these steps.

See slides from Experiment Lifecycle Tools session at GEC15.

p4 for configuration

p21 for mapping of tools to steps

Attachments (4)

Download all attachments as: .zip