| 1 | [[PageOutline]] |
| 2 | |
| 3 | |
| 4 | = GENI Experiment Workflows: Overview = |
| 5 | |
| 6 | |
| 7 | == 1) Types of GENI Experiment Workflows == |
| 8 | |
| 9 | a) From simple to complex |
| 10 | |
| 11 | b) From short-term to long-term |
| 12 | |
| 13 | c) Covers actual experiments, tutorials, and "reference experiments" |
| 14 | |
| 15 | == 2) Ranges of GENI Experiments == |
| 16 | |
| 17 | There will be a wide range of GENI experiment workflows, with different characteristics, including these: |
| 18 | |
| 19 | a) Student solves a class problem |
| 20 | |
| 21 | b) Student executes an on-line tutorial, or follows a reference experiment |
| 22 | |
| 23 | c) Researcher evaluates an algorithm or concept |
| 24 | |
| 25 | d) Researcher evaluates the performance of a configuration |
| 26 | |
| 27 | e) Researcher gathers the results of one or more experiments, and writes a paper |
| 28 | |
| 29 | f) Researcher gathers the results of many experiments, and writes a thesis |
| 30 | |
| 31 | g) Experimenter prototypes a service, without opt-in users |
| 32 | |
| 33 | h) Experimenter prototypes a service, with opt-in users |
| 34 | |
| 35 | i) Experimenter demonstrates a service to selected opt-in users |
| 36 | |
| 37 | j) Experimenter offers a service to many opt-in users for a long period of time |
| 38 | |
| 39 | k) Operator evaluates representative GENI slice performance, such as networking performance, to troubleshoot problems |
| 40 | |
| 41 | l) Operator evaluates representative GENI slice performance, such as networking performance, over an extended period of time, and shares their data with others |
| 42 | |
| 43 | |
| 44 | |
| 45 | = Agenda = |
| 46 | |
| 47 | == 1) Goals (Jeanne) == |
| 48 | |
| 49 | a) Basic GENI test/tutorial/experiment workflow with standardized, self-contained steps |
| 50 | |
| 51 | 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) |
| 52 | |
| 53 | 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. |
| 54 | |
| 55 | d) Because standardized, makes it it easier for the user to understand a tutorial, since all will follow the same outline. |
| 56 | |
| 57 | |
| 58 | == 2) High-level look at workflow (Jeanne) == |
| 59 | |
| 60 | [http://groups.geni.net/syseng/attachment/wiki/ExperimentMgmt/ExpLifecycle-8step.jpg figure] |
| 61 | |
| 62 | |
| 63 | == 3) Review of detailed workflow (Harry) == |
| 64 | |
| 65 | [http://groups.geni.net/geni/wiki/TestTutorialExperimentWorkflow text] |
| 66 | |
| 67 | |
| 68 | == 4) Current mapping between tools and steps (Jeanne) == |
| 69 | |
| 70 | [http://groups.geni.net/syseng/attachment/wiki/ExperimentMgmt/ToolBreakdownTable.jpg figure] |
| 71 | |
| 72 | |
| 73 | == 5) Discussion (all) == |
| 74 | |
| 75 | a) Can we agree on these standardized, self-contained steps? what changes or additions? |
| 76 | |
| 77 | b) Issue: variations with type of users (novice to expert) and thus interfaces (graphical to script); can these be mixed? |
| 78 | |
| 79 | c) Issue: variations between InstaGENI and ExoGENI, between GIMI and GEMINI; is there a common set? |
| 80 | |
| 81 | d) Issue: variations from this basic workflow, to more-specialized workflows; which should be considered? |
| 82 | |
| 83 | e) Next steps? |
| 84 | |
| 85 | = References = |
| 86 | |
| 87 | [http://groups.geni.net/geni/wiki/TestTutorialExperimentWorkflow workflow text] |
| 88 | |
| 89 | [http://groups.geni.net/geni/wiki/TestTutorialExperimentStoryboard related storyboard] |
| 90 | |
| 91 | Currently being used by GIMI and GEMINI I&M projects. |
| 92 | |
| 93 | See [http://groups.geni.net/geni/wiki/GIMIv1.1Tutorial GIMI GEC15 tutorial] that follows these steps. |
| 94 | |
| 95 | See [http://groups.geni.net/geni/wiki/GEC15Agenda/ExperimentLifecycleTools slides] from Experiment Lifecycle Tools session at GEC15. |
| 96 | |
| 97 | p4 for configuration |
| 98 | |
| 99 | p21 for mapping of tools to steps |
| 100 | |
| 101 | |
| 102 | |