Changes between Version 24 and Version 25 of GeniExperiments


Ignore:
Timestamp:
03/25/13 14:33:38 (9 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniExperiments

    v24 v25  
    3838== 2)  Characteristics of GENI Experiment Workflows (Harry) ==
    3939
    40  a)  From a simple to a complex experiment
    41 
    42  b)  By a novice or an expert experimenter
    43 
    44  c)  From a short-term to a long-term experiment
    45 
    46  d)  Using tools with graphical or script-driven interfaces
    47 
    48  e)  Covering actual experiments, tutorials, and "reference experiments" 
    49 
     40a)  From a simple to a complex experiment
     41
     42b)  By a novice or an expert experimenter
     43
     44c)  From a short-term to a long-term experiment
     45
     46d)  Using tools with graphical or script-driven interfaces
     47
     48e)  Covering actual experiments, tutorials, and "reference experiments" 
    5049
    5150
    5251== 3)  Goals for GENI Experiment Workflows (Jeanne and Harry) ==
    5352 
    54  a)  Start with a basic GENI experiment/tutorial/test workflow that uses standardized, self-contained steps, and a format optimized for easy understanding
    55  
    56  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) 
    57  
    58  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.
    59  
    60  d)  Because standardized, with a format optimized for easy understanding, it is easier for the user to understand a tutorial, particularly after completing another GENI tutorial
    61 
    62  e)  Later, produce variations that cover additional types of experiments
     53a)  Start with a basic GENI experiment/tutorial/test workflow that uses standardized, self-contained steps, and a format optimized for easy understanding
     54 
     55b)  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) 
     56 
     57c)  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.
     58 
     59d)  Because standardized, with a format optimized for easy understanding, it is easier for the user to understand a tutorial, particularly after completing another GENI tutorial
     60
     61e)  Later, produce variations that cover additional types of experiments
    6362 
    6463               
    65 == 4)  High-level look at Basic GENI Experiment/Tutorial/Test Workflow (Jeanne)  ==
    66 
    67  [http://groups.geni.net/syseng/attachment/wiki/ExperimentMgmt/ExpLifecycle-8step.jpg  figure] 
    68  
    69 
    70 == 5)  Steps in Basic GENI Experiment/Tutorial/Test Workflow (Harry) ==
    71 
    72  a)  Start with one "Basic GENI Experiment/Tutorial/Test Workflow", and later introduce variations that cover additional types of experiments
    73 
    74  b)  Use to guide:
    75 
    76   *  Experiment management tool design
    77 
    78   *  I&M tool sets
    79 
    80   *  Contents of GENI tutorials
    81 
    82   *  Operational tests, i.e., acceptance tests of GENI racks
    83 
    84  c)  See [http://groups.geni.net/geni/wiki/TestTutorialExperimentWorkflow  basic workflow steps]
    85 
    86  d)  Includes eight steps that are self-contained, which 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)
    87 
    88  e)  Each step typically includes these items:
     64
     65 
     66
     67== 5)  Basic GENI Experiment/Tutorial/Test Workflow (Harry) ==
     68
     69Start with one "Basic GENI Experiment/Tutorial/Test Workflow", and later introduce variations that cover additional types of experiments
     70
     71=== 5.1)  Uses ===
     72
     73Use to guide:
     74
     75a)  Experiment management tool design
     76
     77b)  I&M tool sets
     78
     79c)  Contents of GENI tutorials
     80
     81d)  Operational tests, i.e., acceptance tests of GENI racks
     82
     83=== 5.2)  Graphical view of steps ===
     84
     85[http://groups.geni.net/syseng/attachment/wiki/ExperimentMgmt/ExpLifecycle-8step.jpg  figure] 
     86
     87=== 5.3)  Detailed steps ===
     88
     89[http://groups.geni.net/geni/wiki/TestTutorialExperimentWorkflow  basic workflow steps]
     90
     91=== 5.4)  Summary of steps ===
     92
     93a)  Includes eight steps that are self-contained, which 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)
     94
     95b)  Each step typically includes these items:
    8996
    9097 + Goal, for this step
     
    104111 + Status summary, at completion of the step
    105112
    106  f)  This is consistent with a "best-in-class" example:  web page [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html  Getting Started with Amazon EC2 Linux Instances]
    107 
    108  g)  The following may also be included in the workflow, at the top level or within a step:
     113c)  This is consistent with a "best-in-class" example:  web page [http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html  Getting Started with Amazon EC2 Linux Instances]
     114
     115d)  The following may also be included in the workflow, at the top level or within a step:
    109116
    110117 + FAQs