Changes between Version 20 and Version 21 of TestTutorialExperimentWorkflow


Ignore:
Timestamp:
01/25/13 17:30:50 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TestTutorialExperimentWorkflow

    v20 v21  
    33== Basic GENI Experiment Workflow ==
    44
    5 Version 0.8, January 18, 2013
    6 (after review with Vic and Jeanne on 010913)
     5Version 0.9, January 25, 2013  [[BR]]
     6(after discussion with Vic and Jeanne on 010913)  [[BR]]
     7(after discussion with Jeanne on 012513)  [[BR]]
    78
    89
     
    1920
    2021
    21 === 1)  Design experiment ===
     22=== 1)  Design experiment, and find or write necessary software, rspecs and/or scripts ===
    2223
    23241.1)  Establish experiment goals and strategy for results
     
    31321.5)  Map desired experiment application services to software that is likely to be available, and note gaps.
    3233
    33 1.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
     341.6)  Find, or write, software images/packages/applications, rspecs and/or scripts necessary to realize remaining experiment appication services, identifying repositories and/or gathering into storage service
    3435
    35361.7)  Outline process for the experiment, and capture in a high-level flowchart
     
    37381.8)  Optionally, prototype the experiment using "GENI-in-a-box"
    3839
    39 Experiment management tools used:
     40Experiment management tools utilized:
    4041
    4142 - Gap:  Workflow description creation tool;  consider on-line entry or script
     
    4344 - Option:  "GENI-in-a-box"
    4445
    45  
    46 Persistent services required: 
     46In-slice services utilized: 
     47
     48 
     49Persistent services utilized: 
    4750
    4851 - Repositories for images/packages/software
     
    5053 - GENI Storage Service (admin OOB, web, API)
    5154
    52 Artifacts involved:
    53 
    54  - Gap:  Workflow description;  consider text, DB entries and/or scripts;  consider putting into GENI Storage Service
     55Artifacts utilized:
     56
     57 - Gap:  Artifacts from previous or reference experiments, used as tmeplates for this experiment
     58 
     59 - Gap:  Workflow description;  consider text, DB entries and/or scripts;  consider structure in GENI Storage Service
    5560
    5661 - Gap:  List of all desired experiment resources, including services, software, rspecs, scripts;  consider structure in GENI Storage Service
     
    81862.4)  Verify availability of desired resources in aggregates, including nodes and networking resources, by querying aggregates and/or GMOC;  optionally, reserve scarce resources
    8287
    83 Experiment management tools used:
     88Experiment management tools utilized:
    8489
    8590 - User Workspace environment, including Linux with multiple windows, with browsers and command lines
     
    9095 
    9196 - Gap:  Aggregate resources availability verification tool(s)
    92  
    93 
    94 Persistent services required: 
    95 
    96  - GENI CA (or ?)
     97
     98 
     99In-slice services utilized: 
     100 
     101 
     102Persistent services utilized: 
     103
     104 - GENI CA
    97105 
    98106 - GENI SA
     
    109117 
    110118
    111 Artifacts involved:
     119Artifacts utilized:
    112120
    113121 - Gap:  List of all desired experiment resources, including services, software, rspecs, scripts;  consider structure in GENI Storage Service
     
    144152 
    145153 
    146 Experiment management tools used:
     154Experiment management tools utilized:
    147155
    148156 - User Workspace environment, including Linux with multiple windows, with browsers and command lines
    149157 
    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 
    161 Persistent services required: 
     158 - If using InstaGENI rack(s):  FLACK graphical tool
     159 
     160 - If using ExoGENI rack(s):  Flukes graphical
     161 
     162 - Gap:  one grpahical tool to use for both InstaGENI and ExoGENI racks
     163 
     164 - Option:  Use of GENI CH Portal, then link to graphical assignement tool
     165
     166 - For both InstaGENI and ExoGENI racks, OMNI script-driven tool
     167 
     168 - 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 software loaded using ssh queries or features currently in GUSH
     169
     170 
     171In-slice services utilized: 
     172
     173 - If using GIMI I&M tools:  GIMI measurement point services;  optional GIMI measurement collection and presentation service(s)
     174 
     175 - If using GEMINI I&M tools:  GEMINI measurement point services;  GEMINI measurement sotrage and presentation service(s)
     176
     177 - Experiment application service(s)
     178 
     179 
     180Persistent services utilized: 
    162181
    163182 - Repositories for images/packages/software
     
    168187
    169188
    170 Artifacts involved:
     189Artifacts utilized:
    171190
    172191 - Gap:  List of all desired experiment resources, including services, software, rspecs, scripts;  consider structure in GENI Storage Service
     
    207226
    208227 
    209 Experiment management tools used:
     228Experiment management tools utilized:
    210229
    211230 - If using GEMINI I&M tools:  include configuration in request rspec (p/o Step 3), then run instrumentize script
    212231 
    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
     232 - If 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
    214233 
    215234 - Gap:  Experiment application configuration tool/scripts;  consider using OMF EC and OEDL
    216235
    217 
    218 Persistent services required: 
     236 
     237In-slice services utilized: 
     238
     239 - If using GIMI I&M tools:  GIMI measurement point services;  optional GIMI measurement collection and presentation service(s)
     240 
     241 - If using GEMINI I&M tools:  GEMINI measurement point services;  GEMINI measurement sotrage and presentation service(s)
     242
     243 - Experiment application service(s)
     244 
     245 
     246Persistent services utilized: 
    219247
    220248 - GENI Storage Service (admin OOB, web, API)
     
    228256 - If using GEMINI I&M tools:  GEMINI Portal Service (admin OOB, web, API)
    229257
    230 Artifacts involved:
     258 
     259Artifacts utilized:
    231260
    232261 - Manifest rspec (received)
     
    285314
    286315
    287 Experiment management tools used:
     316Experiment management tools utilized:
    288317
    289318 - User workspace, including windows with scripts and browsers
    290319 
    291  - Gap:  metadata creation and editing service
     320 - Gap:  experiment metadata creation and annotation service
    292321 
    293322 - If using GEMINI I&M tools:  browser;  Gap: consider adding OMF EC with ruby script   
    294323 
    295  - GIMI:  OMF EC with ruby script
    296  
    297  - Experiment:  Gap: consider adding OMF EC with ruby script
    298 
    299 
    300 Persistent services required: 
     324 - If using GIMI tools:  OMF EC with ruby script
     325 
     326 - For xxperiment application:  Gap: consider adding OMF EC with ruby script
     327
     328
     329In-slice services utilized: 
     330
     331 - If using GIMI I&M tools:  GIMI measurement point services;  optional GIMI measurement collection and presentation service(s)
     332 
     333 - If using GEMINI I&M tools:  GEMINI measurement point services;  GEMINI measurement sotrage and presentation service(s)
     334
     335 - Experiment application service(s)
     336 
     337 
     338Persistent services utilized: 
    301339
    302340 - GENI Storage Service (admin OOB, web, API)
     
    312350
    313351
    314 Artifacts involved:
     352Artifacts utilized:
    315353
    316354 - Ruby scripts
     
    353391
    354392
    355 Experiment management tools used:
     393Experiment management tools utilized:
    356394
    357395 - User workspace, including windows with scripts and browsers
     
    359397 - Option if using GIMI I&M tools:  GIMI Portal Service (admin OOB, web, API)
    360398 
    361  - Option if using GEMINI I&M tools:  Unified Network Information Service (UNIS) (web?, API)
    362  
    363399 - Option if using GEMINI I&M tools:  GEMINI Portal Service (admin OOB, web, API)
    364400
     
    371407 - Gap:  metadata creation and editing service
    372408
    373 Persistent services required: 
     409 
     410Persistent services utilized: 
    374411
    375412 - GENI Storage Service (admin OOB, web, API)
    376413
    377414
    378 Artifacts involved:
     415Artifacts utilized:
    379416
    380417 - Measurement data files, with associated metadata files
     
    403440 
    404441 
    405 Experiment management tools used:
     442Experiment management tools utilized:
    406443
    407444 - User Workspace environment, including Linux with multiple windows, with browsers and command lines
    408445 
    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 
     446 
     447 - If using InstaGENI rack(s):  FLACK graphical tool
     448 
     449 - If using ExoGENI rack(s):  Flukes graphical
     450 
     451 - Gap:  one grpahical tool to use for both InstaGENI and ExoGENI racks
     452 
     453 - Option:  Use of GENI CH Portal, then link to graphical assignement tool
     454
     455 - For both InstaGENI and ExoGENI racks, OMNI script-driven tool
     456 
    417457 - 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
    418458
    419 Persistent services required: 
    420 
    421 Artifacts involved:
     459Persistent services utilized: 
     460
     461Artifacts utilized:
    422462
    423463
     
    446486
    447487
    448 Experiment management tools used:
     488Experiment management tools utilized:
    449489
    450490 - User Workspace environment, including Linux with multiple windows, with browsers and command lines
    451491
    452492
    453 Persistent services required: 
     493Persistent services utilized: 
    454494
    455495 - GENI Storage Service (admin OOB, web, API)
     
    458498
    459499
    460 Artifacts involved:
     500Artifacts utilized:
    461501
    462502 - measurement data files, with metadata files
     
    475515 
    476516 - 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