| 1 | = Experimenter Requirements = |
| 2 | |
| 3 | GENI experimenters provide major input to the meso-scale experiments requirements that drive this project. Following is a list of requirements as understood at this time. |
| 4 | |
| 5 | The following requirements '''MUST''' be met within the Plastic Slices Project: |
| 6 | |
| 7 | R001 - Include resources from multiple interoperating aggregates in a slice. [[BR]] |
| 8 | R002 - Allow experimenters to control end-to-end data planes supporting a slice.[[BR]] |
| 9 | R003 - Allow multiple experiment team members to share resources in a slice.[[BR]] |
| 10 | R004 - Operate experiments continuously for three or more months.[[BR]] |
| 11 | R005 - Operate many experiments simultaneously.[[BR]] |
| 12 | R006 - Support non-IP protocol experiments.[[BR]] |
| 13 | R007 - Support comparison of IP and non-IP path results within an experiment.[[BR]] |
| 14 | R008 - Support video and audio applications. [[BR]] |
| 15 | |
| 16 | The following requirements '''MUST''' be met within the next meso-scale experiment project: |
| 17 | |
| 18 | R009 - Support control and data connections from mobile endpoints.[[BR]] |
| 19 | R010 - Support use of cloud services with GENI slices.[[BR]] |
| 20 | R011 - Support up to 1000 hosts in an experiment.[[BR]] |
| 21 | R012 - Support BGPMux in an experiment.[[BR]] |
| 22 | R013 - Support experimenter-controlled load sharing.[[BR]] |
| 23 | R014 - Support bandwidth enforcement (QoS-like functions). [[BR]] |
| 24 | |
| 25 | The following general operations requirements from campuses, operators, and experimenters '''MAY''' be met: |
| 26 | |
| 27 | R015 - Ensure that GENI experiments are compatible with campus security policies.[[BR]] |
| 28 | R016 - Allow campuses to manage access to the resources they contribute to GENI.[[BR]] |
| 29 | R017 - Ensure that the level of effort required from campus IT staff to manage GENI experiments is reasonable, compared to similar research programs.[[BR]] |
| 30 | R018 - Make experiments easier to set up and take down than they were at GEC9.[[BR]] |
| 31 | R019 - Make experiments easier to change (add/delete resources, change data paths) than they were at GEC9.[[BR]] |
| 32 | R020 - Try out operations procedures and policies that can transition to production at-scale use. [[BR]] |
| 33 | |
| 34 | = Requirements Status = |
| 35 | |
| 36 | This section will track the status for each requirement listed above. Note the chart below captures 3 possible states for the requirement being met, they include (Y=Yes, N=No, and P=Partially met.) |
| 37 | |
| 38 | Requirements that '''MUST''' be met for current project: |
| 39 | |
| 40 | || Req # || Type || Met || Known Issues || |
| 41 | || R001 || MUST || Y || ticket#,#|| |
| 42 | || R002 || MUST || P || ticket#,#|| |
| 43 | || R003 || MUST || N || ticket#,#|| |
| 44 | || R004 || MUST || N || ticket#,#|| |
| 45 | || R005 || MUST || N || ticket#,#|| |
| 46 | || R006 || MUST || N || ticket#,#|| |
| 47 | || R007 || MUST || N || ticket#,#|| |
| 48 | || R008 || MUST || N || ticket#,#|| |
| 49 | || R008 || MUST || N || ticket#,#|| |
| 50 | |
| 51 | Requirements that '''MUST''' be met for next project: |
| 52 | |
| 53 | || Req # || Type || Met || Known Issues || |
| 54 | || R009 || MUST || Y || ticket#,#|| |
| 55 | || R010 || MUST || P || ticket#,#|| |
| 56 | || R011 || MUST || N || ticket#,#|| |
| 57 | || R012 || MUST || N || ticket#,#|| |
| 58 | || R013 || MUST || N || ticket#,#|| |
| 59 | || R014 || MUST || N || ticket#,#|| |
| 60 | |
| 61 | Requirements that '''MAY''' for current project: |
| 62 | || Req # || Type || Met || Known Issues || |
| 63 | || R015 || MAY || N || ticket#,#|| |
| 64 | || R016 || MAY || N || ticket#,#|| |
| 65 | || R017 || MAY || N || ticket#,#|| |
| 66 | || R018 || MAY || N || ticket#,#|| |
| 67 | || R019 || MAY || N || ticket#,#|| |
| 68 | || R020 || MAY || N || ticket#,#|| |