Version 3 (modified by, 9 years ago) (diff)


4.2) I&M Use Cases for Experiments, and Support for Experimenters

4.2.1) Goals

Provide a concise but complete definition of I&M Use Cases for Experiments. Include the support that should be available to experimenters, i.e., on-line instructions, examples and help desks.

4.2.2) Team

CO-LEAD Jim Griffioen (U Kentucky)
CO-LEAD Mike Zink (UMass Amherst)
Max Ott (NICTA)
Prasad Calyam (Ohio Super Center)
Harry Mussman (GPO)

4.2.3) Meetings

4.2.4) Vision

Towards Max Ott's vision for experiment support


4.3.5) Basic experiment use case

Basic experiment use case:

1) Setup the experiment in a slice using Experiment Control Tools, via User Portal 1b) Include instrumentation and measurement services in the slice, and utilizing

1b) Gather resources into slice for experiment, include all resources (e.g., hosts) needed for measurements 1c) Load software for experiment, include all software needed for measurements 1d) Configure software for experiment, include all software needed for measurements 1e) As necessary, use persistent GENI services

1) Setup and run experiment using Experiment Control Tools and Experiment Orchestration Service, via User Portal
2) Setup and run measurements using services within slice, and persistent services. Option: get measurement data from persistent MP.
3) Gather MD, and observe during experiment; formulate MDOD.
4) Archive MD with MDOD.
5) Share archived MD with others, per policy included within MDOD.
6) Pull MD out of archive, to analyze and/or visualize.

c) What support must be provided for Experimenters? how?

d) Extended experiment use cases:

1) WiMAX site measurement 2) LEARN/BEN layer 0,1 or 2 real-time measurements 3) Sensor network (radars, power monitors) 4) Measure DiCloud workflow

Attachments (1)

Download all attachments as: .zip