Changes between Version 4 and Version 5 of PlasticSlices/RequirementsTracking


Ignore:
Timestamp:
07/26/11 11:42:52 (11 years ago)
Author:
Josh Smift
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PlasticSlices/RequirementsTracking

    v4 v5  
    33GENI experimenters provide major input to the meso-scale experiments requirements that drive this project.  Following is the list of experimenter requirements as collected through GEC10. Requirements are listed by whether they MUST or MAY be satisfied in the Plastic Slices project, and whether they MUST or MAY be met in a future mesoscale integration project (currently all MAY). 
    44
    5 The following requirements '''MUST''' be met within the Plastic Slices Project:
     5The following requirements '''MUST''' be met within the Plastic Slices project:
    66
    77|| '''Requirement'''                                                         || Met || Known Issues ||
     
    1515|| Support video and audio applications                                      || P   || The types of traffic sent are consistent with audio and video applications, but actual A/V apps were not tested ||
    1616
     17The following general operations requirements from campuses, operators, and experimenters '''MAY''' be met within the Plastic Slices project:
     18
     19|| '''Requirement'''                                                         || Met || Known Issues ||
     20|| Ensure that GENI experiments are compatible with campus security policies || P   || Some recommendations made, no comprehensive review ||
     21|| Allow campuses to manage access to the resources they contribute to GENI  || P   || Some access control, but not very granular ||
     22|| Ensure that the level of effort required from campus IT staff to manage GENI experiments is reasonable, compared to similar research programs || N || ||
     23|| Make experiments easier to set up and take down than they were at GEC9    || Y   || ||
     24|| Make experiments easier to change (add/delete resources, change data paths) than they were at GEC9 || Y || ||
     25|| Try out operations procedures and policies that can transition to production at-scale use || P || Emergency Stop testing is still in progress ||
     26
    1727The following requirements '''MAY''' be met within the next meso-scale experiment project:
    1828
     
    2434|| Support experimenter-controlled load sharing                              || N   || ||
    2535|| Support bandwidth enforcement (QoS-like functions)                        || N   || ||
    26 
    27 The following general operations requirements from campuses, operators, and experimenters '''MAY''' be met:
    28 
    29 || '''Requirement'''                                                         || Met || Known Issues ||
    30 || Ensure that GENI experiments are compatible with campus security policies || P   || Some recommendations made, no comprehensive review ||
    31 || Allow campuses to manage access to the resources they contribute to GENI  || P   || Some access control, but not very granular ||
    32 || Ensure that the level of effort required from campus IT staff to manage GENI experiments is reasonable, compared to similar research programs || N || ||
    33 || Make experiments easier to set up and take down than they were at GEC9    || Y   || ||
    34 || Make experiments easier to change (add/delete resources, change data paths) than they were at GEC9 || Y || ||
    35 || Try out operations procedures and policies that can transition to production at-scale use || P || Emergency Stop testing is still in progress ||