27 | | === 1.2) Slice with GIMI I&M Tools Configuration === |
28 | | |
29 | | |
30 | | === 1.3) Detailed Workflow === |
31 | | |
32 | | |
33 | | === 1.4) GIMI Portal Configuration === |
34 | | |
35 | | |
36 | | === 1.5) GIMI Portal Implementation === |
37 | | |
38 | | |
39 | | === 1.6) Acceptance tasks === |
40 | | |
41 | | === 1.7) Reference Figures === |
| 24 | |
| 25 | |
| 26 | == 2) GIMI v2 Team == |
| 27 | |
| 28 | Mike Zink (UMass Amherst) |
| 29 | |
| 30 | Cong Wang (UMass Amherst) |
| 31 | |
| 32 | Divya Bhat (UMass Amherst) |
| 33 | |
| 34 | Max Ott (NICTA) |
| 35 | |
| 36 | Ilia Baldine (RENCI) |
| 37 | |
| 38 | Shu Huang (RENCI) |
| 39 | |
| 40 | Fraida Fund (NYU Poly) |
| 41 | |
| 42 | Deniz Gurkan (UH) |
| 43 | |
| 44 | Harry Mussman (BBN) |
| 45 | |
| 46 | Jeanne Ohren (BBN) |
| 47 | |
| 48 | Keleigh O'Neil (BBN) |
| 49 | |
| 50 | |
| 51 | == 3) GIMI v2 Meetings/Conference Calls == |
| 52 | |
| 53 | 040113; 4pm EDT |
| 54 | |
| 55 | 040413; 4:30pm EDT |
| 56 | |
| 57 | 041513; 4pm EDT |
| 58 | |
| 59 | 042213; 4pm EDT; discuss iticket for iRODS |
| 60 | |
| 61 | 042913; 4pm EDT; discuss planning meeting 5/2- 5/3 for GIMI Portal; discuss interop status; discuss GSAS status |
| 62 | |
| 63 | 050213 - 050313; define GIMI Portal configuration |
| 64 | |
| 65 | 050913; review workflow, and plan to define GIMI Portal |
| 66 | |
| 67 | 051313; 2-4pm EDT; demo of interop, review workflow |
| 68 | |
| 69 | 052013 - 052113; review goals; review and update workflow; define entities and interfaces; define init script; define GIMI portal |
| 70 | |
| 71 | 052913; 4pm EDT; review documentation of workflow and designs; agree on tasks |
| 72 | |
| 73 | 061013; 2-4pm EDT; demo; end of sprint 1 (S1) |
| 74 | |
| 75 | 062413; 4pm EDT; demo; end of sprint 2 (S2) |
| 76 | |
| 77 | 070813; 2-4pm EDT; demo; end of sprint 3 (S2) |
| 78 | |
| 79 | 072113 - 072313 is GEC17; v2 software released after testing; integrated tutorials presented |
| 80 | |
| 81 | |
| 82 | == 4) GIMI v2 Plan == |
| 83 | |
| 84 | * Started 032013 |
| 85 | * Revised 032913 |
| 86 | * Revised 040213 after 040113 call, and after GEMINI call on 040213 |
| 87 | * Revised 040513 after discussion with Mike on 040413 |
| 88 | * Revised after 041513 and 042213 calls, and discussions with Mike. |
| 89 | * Revised after 042913 call |
| 90 | * Revised after 052113 meeting |
| 91 | |
| 92 | |
| 93 | === 4.1) Reference Figures === |
61 | | == 2) Team == |
62 | | |
63 | | Mike Zink (UMass Amherst) |
64 | | |
65 | | Cong Wang (UMass Amherst) |
66 | | |
67 | | Divya Bhat (UMass Amherst) |
68 | | |
69 | | Max Ott (NICTA) |
70 | | |
71 | | Ilia Baldine (RENCI) |
72 | | |
73 | | Shu Huang (RENCI) |
74 | | |
75 | | Fraida Fund (NYU Poly) |
76 | | |
77 | | Deniz Gurkan (UH) |
78 | | |
79 | | Harry Mussman (BBN) |
80 | | |
81 | | Jeanne Ohren (BBN) |
82 | | |
83 | | Keleigh O'Neil (BBN) |
84 | | |
85 | | |
86 | | == 3) Planning and Status Meetings/Conference Calls == |
87 | | |
88 | | 040113; 4pm EDT |
89 | | |
90 | | 040413; 4:30pm EDT |
91 | | |
92 | | 041513; 4pm EDT |
93 | | |
94 | | 042213; 4pm EDT; discuss iticket for iRODS |
95 | | |
96 | | 042913; 4pm EDT; discuss planning meeting 5/2- 5/3 for GIMI Portal; discuss interop status; discuss GSAS status |
97 | | |
98 | | 050213 - 050313; define GIMI Portal configuration |
99 | | |
100 | | 050913; review workflow, and plan to define GIMI Portal |
101 | | |
102 | | 051313; 2-4pm EDT; demo of interop, review workflow |
103 | | |
104 | | 052013 - 052113; review goals; review and update workflow; define entities and interfaces; define init script; define GIMI portal |
105 | | |
106 | | 052913; 4pm EDT; review documentation of workflow and designs; agree on tasks |
107 | | |
108 | | 061013; 2-4pm EDT; demo; end of sprint 1 (S1) |
109 | | |
110 | | 062413; 4pm EDT; demo; end of sprint 2 (S2) |
111 | | |
112 | | 070813; 2-4pm EDT; demo; end of sprint 3 (S2) |
113 | | |
114 | | 072113 - 072313 is GEC17; v2 software released after testing; integrated tutorials presented |
115 | | |
116 | | |
117 | | == 4) GIMI v2 Tasks == |
118 | | |
119 | | * Started 032013 |
120 | | * Revised 032913 |
121 | | * Revised 040213 after 040113 call, and after GEMINI call on 040213 |
122 | | * Revised 040513 after discussion with Mike on 040413 |
123 | | * Revised after 041513 and 042213 calls, and discussions with Mike. |
124 | | * Revised after 042913 call |
125 | | * Revised after 052113 meeting |
126 | | |
127 | | |
128 | | 1) By 4/15: /cleanup/checkin/test/document current code [[BR]] |
129 | | What needs work? [[BR]] |
130 | | |
131 | | 2) Agree on goals: [[BR]] |
132 | | a) GIMI (also GEMINI) to work with both ExoGENI and InstaGENI [[BR]] |
133 | | b) Consistent user experience, both racks, both sets of I&M tools [[BR]] |
134 | | c) Implement basic workflow per http://groups.geni.net/geni/wiki/GeniExperiments#a5StepsinBasicGENIExperimentTutorialTestWorkflowHarry and http://groups.geni.net/geni/wiki/TestTutorialExperimentWorkflow [[BR]] |
135 | | Issue: what range of workflows must be supported? small (classroom exercise); medium (research experiment); large (long-running service, with opt-in) [[BR]] |
136 | | Answer: eventually all of these, but with an emphasis on small and medium at this time; should have a way to extend medium to large; Sol 4 calls for shakedown experiments that are large [[BR]] |
137 | | d) Easy to setup basic set of measurements (towards unified experiment environment) [[BR]] |
138 | | Issue: what are basic set of measurements? [[BR]] |
139 | | Answer: at least "passive host measurements", and "mesh of pings between nodes" [[BR]] |
140 | | e) Easy to mix-and-match tools, as go from step to step, with automatic transfer of info between steps/tools [[BR]] |
141 | | f) Easy to configure and then visualize (graph) measurements, starting from a graphical (or tabular) view of the topology of resources [[BR]] |
142 | | Issue: But, starting from a starting from a graphical (or tabular) view of the topology of resources to configure desired measurements is not always best. For example, for a classroom exercise, may want a pre-defined experiment, with a pre-define measurement configuration. For example, for a large experiment with 100s of nodes, it is not practical or useful to drive measurements from a graphical view of the topology; want to do everything with a script. [[BR]] |
143 | | Answer: Should be easy to configure and then visualize (graph) measurements, but the mechanism will likely differ depending on the type of experiment: small (predefined), medium, large. Nonetheless, should provide a method to serve all three that is not cumbersome for the experimenter. For a large experiment, will need to be able to use a script. [[BR]] |
144 | | h) Ability to simultaneously run multiple measurement sessions (e.g., passive host, mesh of pings, intermittent iperf, and experiment specific), each with multiple measurements and multiple graphs, during an experiment [[BR]] |
145 | | i) Stay consistent with Spiral 5 GIMI SOW [[BR]] |
146 | | |
147 | | 3) Build workflow for GIMI to work on both InstaGENI and ExoGENI [[BR]] |
| 113 | === 4.2) GIMI v2 Key Parameters === |
| 114 | |
| 115 | * [1] user_identity |
| 116 | * [2] user_credentials |
| 117 | * [3] slice_id |
| 118 | * [4] slice_node_names |
| 119 | * [5] slice_node_meas_extens |
| 120 | |
| 121 | * [6] slice_request_rspec |
| 122 | * [7] sliver_manifest_rspecs |
| 123 | * [8] sliver_manifest_descriptors |
| 124 | * [9] project_id |
| 125 | * [10] experiment_id |
| 126 | |
| 127 | * [11] proj_exper_step_descriptors |
| 128 | * [12] user_irods_home_directory |
| 129 | * [13] user_irods_target_directory |
| 130 | * [14] user_irods_target_iticket |
| 131 | * [15] measure_task_id |
| 132 | |
| 133 | * [16] meas_task_omf_script |
| 134 | * [17] meas_task_omf_script_param |
| 135 | * [18] meas_task_descriptor |
| 136 | * [19] meas_data_object |
| 137 | * [20] meas_data_descriptor |
| 138 | |
| 139 | |
| 140 | === 4.3) Build workflow for GIMI to work on both InstaGENI and ExoGENI === |
| 141 | |