| 22 | | c) Focus on target aggregates including protoGENI sites (e.g., Utah) and InstaGENI racks. |
| | 23 | j) Support installing both MPs and GN on InstaGENI VMs. |
| | 24 | |
| | 25 | k) Provide a set of "usable tools” for experimenters, to be presented in a tutorial at GEC15. |
| | 26 | |
| | 27 | l) Use reference workflow as a guide for GEC15 tutorial. |
| | 28 | |
| | 29 | m) Show how to setup slice in GEC15 tutorial using FLACK to formulate request rspec, and OMNI to obtain resources via GENI AM API. |
| | 30 | |
| | 31 | n) Include a realistic reference experiment in the GEC15 tutorial, and include a convenient orchestration method. |
| | 32 | |
| | 33 | o) Enalbe passive host measurements and basic active network measurements (i.e., ping) for the duration of the experiment run, and arrange for experimenter to view measurements in real time, so that they can verify that experiment run is proceeding as expected. |
| | 34 | |
| | 35 | p) Enable active network measurements (i.e., iperf) for a short time at the start of the experiment run, and arrange for experimenter to view measurements in real time, so that they can verify the continuity of their slice, and that it can handle the expected traffic. |
| | 36 | |
| | 37 | q) Finally, orchestrate the reference experiment, and collect desired measurements from within the experiment; alternately, use active network measurements (i.e., iperf) to generate and measure traffic that flows through reference experiment topology. |
| | 38 | |
| | 39 | r) After experiment run finishes, arrange for experimenter to format and view measurements that have been collected during run, to verify that experiment has been successfully completed. |
| | 40 | |
| | 41 | s) After experiment finishes, allow experimenter to push measurements that have been collected during run into the iRODS storage service; later, allow them to retrieve these measurements and view them again. Note: this is currently limited to Type-1 passive host measurements (INSTOOLS modules). |
