Changes between Version 18 and Version 19 of TestTutorialExperimentWorkflow


Ignore:
Timestamp:
01/18/13 15:27:09 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TestTutorialExperimentWorkflow

    v18 v19  
    33== Basic Experiment Workflow ==
    44
    5 Version 0.9, January 8, 2013
    6 
     5Version 0.8, January 18, 2013
     6(after review with Vic and Jeanne on 010913)
    77
    88
     
    13130.2)  Goals and strategy for results
    1414
    15 0.3)  Configuration
    16 
    17 0.4)  Process  (flow chart)
     150.3)  Configuration  (e.g, topology of slice resources for experiment)
     16
     170.4)  Process  (i.e., flow chart of experiment)
    1818
    1919
     
    23231.1)  Establish experiment goals and strategy for results
    2424
    25 1.2)  Design configuration of experiment to meet goals, including topology, desired resources, desired tools and desired persistent services;  consider previous, or reference, experiments as guides
    26 
    27 1.3)  Map desired resources to aggregates that are likely to be available
    28 
    29 1.4)  Map desired tools to tools that are available, and identify necessary persistent services.
    30 
    31 1.5)  Map desired in-slice services to software that is likely to be available.
    32 
    33 1.6)  Find, or design and code, software images/packages/applications, rspecs and/or scripts necessary to realize experiment, identifying repositories and/or gathering into storage service
     251.2)  Design configuration of experiment to meet goals, including topology, desired resources, desired tools and desired experiment application services;  consider previous, or reference, experiments as guides;  capture in a high-level configuration drawing or list
     26
     271.3)  Map desired resources (i.e., computing and networking resources) to aggregates that are likely to be available
     28
     291.4)  Map desired tools (i.e., I&M tools) to tools that are available, and identify necessary persistent services.
     30
     311.5)  Map desired experiment application services to software that is likely to be available, and note gaps.
     32
     331.6)  Find, or design and code, software images/packages/applications, rspecs and/or scripts necessary to realize remaining experiment appication services, identifying repositories and/or gathering into storage service
    3434
    35351.7)  Outline process for the experiment, and capture in a high-level flowchart
     
    3939Experiment management tools used:
    4040
    41  - Gap:  workflow description creation tool;  option:  extend to workflow execution tool [Ref:  GRID Generic Workflow Execution Service]
     41 - Gap:  Workflow description creation tool;  consider on-line entry or script
    4242 
    4343 - Option:  "GENI-in-a-box"
     
    4646Persistent services required: 
    4747
    48  - repositories for images/packages/software
    49 
    50  - GENI Storage Service (admin OOB, web, API)
    51 
    52 Artifacts involved:
    53 
    54  - Gap:  Workflow description  [Ref:  OEDL;  Ref: GRID Generic Workflow Description Language (GWorkflowDL) ]
    55 
    56  - Gap:  List of all experiment resources, including services, software, rspecs, scripts, others?
    57 
    58  - images/packages/software for GIMI, GEMINI, and/or experiment
    59  
    60 Status at completion:
    61 
    62  - experiment goals and strategy for results extablished
    63  
    64  - experiment configuration realized, and mapped into avaialble resources, etc.
    65  
    66  - Found or designed and coded software, rspecs and scripts necessary for experiment
    67 
    68  - experiment process outlined
     48 - Repositories for images/packages/software
     49
     50 - GENI Storage Service (admin OOB, web, API)
     51
     52Artifacts involved:
     53
     54 - Gap:  Workflow description;  consider text, DB entries and/or scripts;  consider putting into GENI Storage Service
     55
     56 - Gap:  List of all desired experiment resources, including services, software, rspecs, scripts;  consider structure in GENI Storage Service
     57
     58 - Images/packages/software for tools (i.e., GIMI and/or GEMINI I&M tools)
     59 
     60 - Images/packages/software for experiment application services
     61 
     62Status at completion:
     63
     64 - Experiment goals and strategy for results extablished
     65 
     66 - Experiment configuration identified, and mapped into avaialble resources, etc.
     67 
     68 - Found or designed and coded software, rspecs and scripts necessary for experiment application services
     69
     70 - Experiment process outlined
    6971
    7072 
    7173=== 2)  Establish experiment management environment ===
    7274
    73 2.1)  Establish user workspace environment, as repository for artifacts and experiment management tools
     752.1)  Establish user workspace environment, as repository for experiment management tools and local copy of some artifacts
    7476
    75772.2)  Gather necessary keys, passwords, certificates and credentials
     
    8183Experiment management tools used:
    8284
    83  - User Workspace environment, including linux with multiple windows, for browsers and command lines
     85 - User Workspace environment, including Linux with multiple windows, with browsers and command lines
    8486
    8587 - Option:  use GENI CH Portal to obtain certificates, etc.
     
    8789 - Gap:  Persistent services availability verification tool
    8890 
    89  - Gap:  Aggregate resources availabilityy verification tool(s)
     91 - Gap:  Aggregate resources availability verification tool(s)
    9092 
    9193
     
    9698 - GENI SA
    9799 
    98  - GENI Messaging Service  (API)
    99  
    100  - GENI Storage Service (admin OOB, web, API)
    101  
    102  - GIMI Portal Service (admin OOB, web, API)
    103  
    104  - GEMINI Portal Service (admin OOB, web, API)
    105  
    106  - Unified Network Information Service (UNIS) (web?, API)
    107 
    108 
    109 Artifacts involved:
    110 
    111  - Gap:  List of all experiment resources, including services, software, rspecs, scripts, others?
     100 - GENI Storage Service (admin OOB, web, API)
     101 
     102 - If using GIMI I&M tools:  GENI Messaging Service  (API)
     103 
     104 - If using GIMI I&M tools:  GIMI Portal Service (admin OOB, web, API)
     105 
     106 - If using GEMINI I&M tools:  Unified Network Information Service (UNIS) (web?, API)
     107 
     108 - If using GEMINI I&M tools:  GEMINI Portal Service (admin OOB, web, API)
     109 
     110
     111Artifacts involved:
     112
     113 - Gap:  List of all desired experiment resources, including services, software, rspecs, scripts;  consider structure in GENI Storage Service
    112114 
    113115 - Experimenter usernames/passwords, certificates, keys, credentials
     
    115117Status at completion:
    116118
    117  - established user workspace environment, as repository for artifacts and experiment management tools
    118  
    119  - gathered necessary keys, passwords, certificates and credentials
    120 
    121  - verified availability of necessary persistent services, and access to those services
    122 
    123  - verified availability of desired resources in aggregates
    124  
    125  - optionally, reserved scarce resources
     119 - Established user workspace environment, as repository for experiment management tools and local copy of some artifacts
     120 
     121 - Gathered necessary keys, passwords, certificates and credentials for experimenter
     122
     123 - Verified availability of necessary persistent services, and access to those services
     124
     125 - Verified availability of desired resources in aggregates
     126 
     127 - Optionally, reserved scarce resources
    126128
    127129
     
    1321343.1)  Select target aggregates
    133135
    134 3.2)  Select desired software images/packages for I&M and experiment services
     1363.2)  Select desired software images/packages for I&M tools and experiment application services
    135137
    1361383.3)  Formulate slice topology for experiment, and build request rspec
    137139
    138 3.4)  Acquire resources and load images/packages for I&M and experiment services
    139 
    140 3.5)  Verify slice with desired topology and installed images/packages/software for I&M and experiment services on nodes and on networking resources
    141 
    142  
    143  
    144 Experiment management tools used:
    145 
    146  - InstaGENI:  FLACK with OMNI
    147  
    148  - ExoGENI:  Flukes
    149  
    150  - Towards one tool for both InstaGENI and ExoGENI:  FLACK with OMNI
    151  
    152  - Option:  GENI CH Portal, plus FLACK with OMNI
    153 
    154  - Gap:  Topology and installation verification tool(s)  [Note:  some provided in FLACK, and some in GUSH]
    155  
    156 
    157 Persistent services required: 
    158 
    159  - repositories for images/packages/software
     1403.4)  Acquire slice of resources and load images/packages for I&M and experiment application services
     141
     1423.5)  Verify expected slice topology and installed images/packages/software for I&M and experiment services, on computing and on networking resources, based on manifest rspec returned from aggregates
     143
     144 
     145 
     146Experiment management tools used:
     147
     148 - User Workspace environment, including Linux with multiple windows, with browsers and command lines
     149 
     150 - If using InstaGENI rack(s):  FLACK with OMNI
     151 
     152 - If using ExoGENI rack(s):  Flukes
     153 
     154 - Towards one tool to use for both InstaGENI and ExoGENI racks:  FLACK with OMNI
     155 
     156 - Option:  Use of GENI CH Portal, plus FLACK with OMNI
     157
     158 - Gap:  Topology and installation verification tool(s);  could use features in FLACK;  could push manifest rspec to UNIS, and use a GUI on UNIS to visualize topology;  could verify correct softwar loaded using ssh queries or features currently in GUSH
     159 
     160
     161Persistent services required: 
     162
     163 - Repositories for images/packages/software
    160164 
    161165 - Unified Network Information Service (UNIS) (stores experiment topology, based on manifest rspec)
     
    166170Artifacts involved:
    167171
    168  - Gap:  List of all experiment resources, including services, software, rspecs, scripts, others?
    169  
    170  - images/packages/software for GIMI, GEMINI, and/or experiment
    171  
    172  - request rspec (build and then submit)
    173  
    174  - manifest rspec (receive)
    175 
    176 
    177 Status at completion:
    178 
    179  - obtained slice of GENI resources, with desired topology
    180  
    181  - installed images/packages/software for I&M and experiment services on nodes and on networking resources
     172 - Gap:  List of all desired experiment resources, including services, software, rspecs, scripts;  consider structure in GENI Storage Service
     173 
     174 - Images/packages/software for I&M tools and experiment application services
     175 
     176 - Request rspec (build and then submit)
     177 
     178 - Manifest rspec (received)
     179
     180
     181Status at completion:
     182
     183 - Obtained slice of GENI resources, with desired topology
     184 
     185 - Installed images/packages/software for I&M and experiment services on computing and on networking resources
    182186
    183187
     
    205209Experiment management tools used:
    206210
    207  - GEMINI:  include configuration in request rspec (p/o Step 3), then run instrumentize script
    208  
    209  - GIMI:  p/o configuration done in post-boot scripts (p/o Step 3), then completed using OMF EC with ruby scripts
    210  
    211  - Gap:  Experiment configuration tool/scripts
    212 
    213 
    214 Persistent services required: 
    215 
    216 
    217 Artifacts involved:
    218 
    219  - manifest rspec (receive)
     211 - If using GEMINI I&M tools:  include configuration in request rspec (p/o Step 3), then run instrumentize script
     212 
     213 - I using GIMI I&M tools:  p/o configuration is done in post-boot scripts (p/o Step 3), then completed using OMF EC with ruby scripts
     214 
     215 - Gap:  Experiment application configuration tool/scripts;  consider using OMF EC and OEDL
     216
     217
     218Persistent services required: 
     219
     220 - GENI Storage Service (admin OOB, web, API)
     221 
     222 - If using GIMI I&M tools:  GENI Messaging Service  (API)
     223 
     224 - If using GIMI I&M tools:  GIMI Portal Service (admin OOB, web, API)
     225 
     226 - If using GEMINI I&M tools:  Unified Network Information Service (UNIS) (web?, API)
     227 
     228 - If using GEMINI I&M tools:  GEMINI Portal Service (admin OOB, web, API)
     229
     230Artifacts involved:
     231
     232 - Manifest rspec (received)
    220233
    221234 
     
    226239 - I&M services have been bound together and initialized, so that they are ready to run and collect measurement data
    227240 
    228  - experiment services have been configured to realize desired topology and functionality
    229  
    230  - experiment services have been bound together and initialized, so that they are ready to run and collect measurement data
     241 - Experiment application services have been configured to realize desired topology and functionality
     242 
     243 - Experiment application services have been bound together and initialized, so that they are ready to run and collect measurement data
    231244 
    232245 
     
    2352485.1)  Inititate basic measurements
    236249
    237  - start basic host measurements to verify functionality of hosts
    238  
    239  - start basic ping active network measurements to verify topology of slice
     250 - start basic host measurements to verify functionality of all hosts
     251 
     252 - start a set of ping active network measurements to verify topology of slice
    240253
    241254 - observe measurements with a real-time presentation service
     
    243256 - continue measurements throughout duration of the experiment, to verify functionality of hosts and topology of slice
    244257 
    245 5.2)  Verify topology and bandwidth/performance of networking resources (continuity test)
     2585.2)  Verify topology and bandwidth/performance of networking resources using active networking measurements (do a "continuity test")
    246259
    247260 - configure and start active network measurements (i.e., iperf) in a configuration designed to verify ability of slice to carry traffic expected during experiment
     
    274287Experiment management tools used:
    275288
    276  - User workspace, scripts and browser
     289 - User workspace, including windows with scripts and browsers
    277290 
    278291 - Gap:  metadata creation and editing service
    279292 
    280  - GEMINI:  browser;  Gap: consider adding OMF EC with ruby script   
     293 - If using GEMINI I&M tools:  browser;  Gap: consider adding OMF EC with ruby script   
    281294 
    282295 - GIMI:  OMF EC with ruby script
     
    287300Persistent services required: 
    288301
    289  - GENI Messaging Service  (API)
    290  
    291  - GENI Storage Service (admin OOB, web, API)
    292  
    293  - GIMI Portal Service (admin OOB, web, API)
    294  
    295  - GEMINI Portal Service (admin OOB, web, API)
    296  
    297  - Unified Network Information Service (UNIS) (web?, API)
    298 
    299 
    300 Artifacts involved:
    301 
    302  - ruby scripts
    303  
    304  - measurement data files, with metadata files
     302 - GENI Storage Service (admin OOB, web, API)
     303 
     304 - If using GIMI I&M tools:  GENI Messaging Service  (API)
     305 
     306 - If using GIMI I&M tools:  GIMI Portal Service (admin OOB, web, API)
     307 
     308 - If using GEMINI I&M tools:  Unified Network Information Service (UNIS) (web?, API)
     309 
     310 - If using GEMINI I&M tools:  GEMINI Portal Service (admin OOB, web, API)
     311
     312
     313
     314Artifacts involved:
     315
     316 - Ruby scripts
     317 
     318 - Measurement data files, with associated metadata files
    305319 
    306320
     
    322336=== 6)  Analyze experiment results, and decide on next step(s)  ===
    323337
    324  - if necessary, retrieve measurement results from storage service
    325  
    326  - analyze measurement results to evaluate experiment results
     338 - if necessary, retrieve measurement results from storage service, in a standardized format
    327339 
    328340 - as desired, format to facilitate analysis
    329341 
    330342 - as desired, visualize using a presentation serivce to facilitate analysis
     343 
     344 - analyze measurement results to evaluate experiment results
    331345 
    332346 - decide whether experiment goals have been met or not
     
    341355Experiment management tools used:
    342356
    343  - User workspace, scripts and browser
    344  
     357 - User workspace, including windows with scripts and browsers
     358 
     359 - Option if using GIMI I&M tools:  GIMI Portal Service (admin OOB, web, API)
     360 
     361 - Option if using GEMINI I&M tools:  Unified Network Information Service (UNIS) (web?, API)
     362 
     363 - Option if using GEMINI I&M tools:  GEMINI Portal Service (admin OOB, web, API)
     364
     365 - Gap:  presentation tools;  consider r and gnuplot;  others?
     366
     367 - Gap:  analysis tools;  which?
     368 
     369 - Option:  a different workspace, better configured for analyzing results
     370
    345371 - Gap:  metadata creation and editing service
    346  
    347  - Gap:  analysis tools;  consider ?
    348  
    349  - Gap:  presentation tools;  consider r and newplot
    350 
    351 
    352 Persistent services required: 
    353 
    354  - GENI Storage Service (admin OOB, web, API)
    355  
    356  - GIMI Portal Service (admin OOB, web, API)
    357  
    358  - GEMINI Portal Service (admin OOB, web, API)
    359  
    360  - Unified Network Information Service (UNIS) (web?, API)
    361 
    362 
    363 Artifacts involved:
    364 
    365  - measurement data files, with metadata files
    366 
    367 Status at completion:
    368 
    369  - current set of experiment measurement results have been analyzed, formatted and/or visaualized
     372
     373Persistent services required: 
     374
     375 - GENI Storage Service (admin OOB, web, API)
     376
     377
     378Artifacts involved:
     379
     380 - Measurement data files, with associated metadata files
     381
     382Status at completion:
     383
     384 - Current set of experiment measurement results have been analyzed, formatted and/or visualized
    370385 
    371386 - given current set of experiment measurement results, have decided whether experiemnt goals have been met or not, whether additional experiment runs are required or not, and whether slice resources can now be released
     
    390405Experiment management tools used:
    391406
    392  - User workspace, scripts and browser
    393 
    394  - InstaGENI:  FLACK with OMNI
    395  
    396  - ExoGENI:  Flukes
    397  
    398  - Common:  FLACK with OMNI
    399  
    400  - Option:  GENI CH Portal, plus FLACK with OMNI
    401 
    402  - Gap:  Topology and installation verification tool(s)
     407 - User Workspace environment, including Linux with multiple windows, with browsers and command lines
     408 
     409 - If using InstaGENI rack(s):  FLACK with OMNI
     410 
     411 - If using ExoGENI rack(s):  Flukes
     412 
     413 - Towards one tool to use for both InstaGENI and ExoGENI racks:  FLACK with OMNI
     414 
     415 - Option:  Use of GENI CH Portal, plus FLACK with OMNI
     416
     417 - Gap:  Topology and installation verification tool(s);  could use features in FLACK;  could push manifest rspec to UNIS, and use a GUI on UNIS to visualize topology;  could verify correct softwar loaded using ssh queries or features currently in GUSH
    403418
    404419Persistent services required: 
     
    433448Experiment management tools used:
    434449
    435  - User workspace, scripts and browser
     450 - User Workspace environment, including Linux with multiple windows, with browsers and command lines
    436451
    437452
     
    448463 
    449464 - object containing selected artifacts, with metadata
     465 
    450466Status at completion:
    451467
     
    459475 
    460476 - when object can be shared with others, it can be searched from the Internet, and retrieved using the handle identifier
     477
     478
     479
     480
     481
     482
     483
     484
     485
     486
     487
     488
     489
     490
     491
     492
     493
     494
     495
     496
     497
     498
     499