57 | | == 3) Summary of GIMI design goals for Spiral 5, and current status == |
58 | | 8:40am [[BR]] |
59 | | '''PI''' Michael Zink, University of Massachusetts at Amherst (mailto:zink@ecs.umass.edu) [[BR]] |
60 | | '''Co-PI''' Max Ott, NICTA (mailto:max.ott@nicta.com.au) [[BR]] |
61 | | '''Key personnel''' Ilia Baldine, RENCI (mailto:ibaldin@renci.org) [[BR]] |
62 | | |
63 | | [wiki:GIMI GIMI wiki] [[BR]] |
64 | | [http://gimi.ecs.umass.edu/ GIMI website at UMass Amherst] [[BR]] |
65 | | |
66 | | Goals [[BR]] |
67 | | * Starts with OML, and provides easy-to-use tools for GENI environment [[BR]] |
68 | | |
69 | | * First focus: I&M use cases for experiments, with default OML Client in nodes that gathers passive measurements like INSTOOLS, and provides basic node-to-node connectivity tests using ping and iperf [[BR]] |
70 | | * Second focus: I&M use cases for infrastructure measurement [[BR]] |
71 | | * Later focus: add sensor measurement data, carried in data network [[BR]] |
72 | | |
73 | | * Spiral 4 supported aggregates: ORCA servers/VMs and ExoGENI (RENCI) racks [[BR]] |
74 | | * Later, support: WiMAX sites [[BR]] |
75 | | * Spiral 5 supported aggregates: protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]] |
76 | | |
77 | | * Introduces XML messaging service, with pub/sub, in public IP space [[BR]] |
78 | | * Introduces iRODS service, as a measurement data archive. [[BR]] |
79 | | * Introduces IREEL portal service, for measurement data analysys and presentation. [[BR]] |
80 | | |
81 | | |
82 | | Summary: [[BR]] |
83 | | |
84 | | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/GIMI%20GEC%2014%20I%26M%20Session.pptx GIMI architecture, design and status at GEC14; plan for GEC-14 tutorial; next steps during Spiral 5] [[BR]] |
85 | | * For more information, attend or audit [http://groups.geni.net/geni/wiki/GIMIv1.0Tutorial GIMI v1.0 tutorial] [[BR]] |
86 | | |
87 | | |
88 | | |
89 | | == 4) Summary of GEMINI design goals for Spiral 5, and current status == |
90 | | 8:50am [[BR]] |
91 | | '''PI''' Martin Swany, Indiana University (mailto:swany@iu.edu) [[BR]] |
92 | | '''Co-PI''' Chris Small, Indiana University (mailto:chsmall@indiana.edu) [[BR]] |
93 | | '''Co-PI''' James Griffioen, University of Kentucky (mailto:griff@netlab.uky.edu) [[BR]] |
94 | | '''Co-PI''' Zongming Fei, University of Kentucky (mailto:fei@netlab.uky.edu) [[BR]] |
95 | | |
96 | | [wiki:GEMINI GEMINI wiki] [[BR]] |
97 | | |
98 | | Goals [[BR]] |
99 | | |
100 | | * Includes LAMP code and features in GEMINI tools, to provides flexible tools based on perfSONAR for active infrastructure measurements [[BR]] |
101 | | * Includes INSTOOLS code and features in GEMINI tools, to gather basic host measurements [[BR]] |
102 | | * Later, integrates LAMP and INSTOOLS code and features into new code base for GEMINI tools. [[BR]] |
103 | | |
104 | | * First focus: I&M use cases for infrastructure measurement [[BR]] |
105 | | * Include sharing of data with other users (e.g., operators), at an interface with authorization using a GENI credential [[BR]] |
106 | | * Show how to monitor clusters/racks [[BR]] |
107 | | * Show how to measure Layer 2 and OpenFlow paths (with input from OnTimeMeasure project) [[BR]] |
108 | | |
109 | | * Second focus: I&M use cases for experiments [[BR]] |
110 | | * Gather basic host measurements (as was done by INSTOOLS using SNMP) [[BR]] |
111 | | * Show how to gather customized data from applications (as provided by OML Client) [[BR]] |
112 | | |
113 | | * Spiral 4 supported aggregates: protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]] |
114 | | * Spiral 5 supported aggregates: ORCA servers/VMs and ExoGENI (RENCI) racks [[BR]] |
115 | | |
116 | | * Continues INSTOOLS portal service, to find GUIs [[BR]] |
117 | | * Continues LAMP local and global Unified Network Information Service (UNIS), to register available measurement data, and network topology [[BR]] |
118 | | |
119 | | Summary [[BR]] |
120 | | |
121 | | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/GEMINI%20Overview%20and%20Direction-GEC14.pptx GEMINI architecture, design and status at GEC14; plan for GEC-14 tutorial; next steps during Spiral 5] [[BR]] |
122 | | * For more information, attend or audit [http://groups.geni.net/geni/wiki/GEMINITutorial GEMINI v1.0 tutorial] [[BR]] |
123 | | |
178 | | === S3) GIMI Portal Service === |
179 | | 9:30am [[BR]] |
180 | | |
181 | | Max Ott and Christoph Dwertmann (NICTA); Mike Zink and Cong Wang (UMass Amherst) [[BR]] |
182 | | |
183 | | Tasks |
184 | | * Establish IREEL service, to provide measurement analysis and presentation functions, starting with GIMI project [[BR]] |
185 | | * Extend/change to become Lab wiki service [[BR]] |
186 | | |
187 | | Summary |
188 | | * IREEL service has been established at NICTA [[BR]] |
189 | | * IREEL service has been established at UMassAmherst [[BR]] |
190 | | * Current configuration [ slides] [[BR]] |
191 | | * Proposed configuration [ slides] [[BR]] |
192 | | * Operations plan [ slides] [[BR]] |
193 | | |
194 | | Discussion |
195 | | * Who is lead? [[BR]] |
196 | | * How are partitions for different users managed? [[BR]] |
197 | | * How is authorization for a user done? [[BR]] |
198 | | * Can IREEL be used to provide other functions, e.g., experiment meangement? if so, how? [[BR]] |
199 | | * Will the GEMINI project want to use the IREEL service? [[BR]] |
200 | | * Will other parts of GENI want to use the IREEL service? [[BR]] |
201 | | * Do we need a breakout session for further discussion? when? [[BR]] |
202 | | |
203 | | === S4) GEMINI portal-to-GUIs Service === |
204 | | 9:40am [[BR]] |
205 | | |
206 | | Charles Carpenter (U Kentucky) [[BR]] |
207 | | |
208 | | Tasks: |
209 | | * Continue INSTOOLS portal-to-GUIs service, to allow user to locate GUIs within their slice, for use with INSTOOLS and GEMINI tools [[BR]] |
210 | | |
211 | | Summary |
212 | | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/GEMINI%20Portal.ppt current GEMINI portal service configuration] [[BR]] |
213 | | |
214 | | Discussion |
215 | | * Who is lead? [[BR]] |
216 | | * How are partitions for different users managed? [[BR]] |
217 | | * How is authorization for a user done? [[BR]] |
218 | | * What additional features are under consideration? [[BR]] |
219 | | * Will the GIMI project want to use the INSTOOLS portal-to-GUIs service? [[BR]] |
220 | | * Will other parts of GENI want to use the INSTOOLS portal-to-GUIs service? [[BR]] |
221 | | * Do we need a breakout session for further discussion? when? [[BR]] |
222 | | |
223 | | === S5) UNIS Service === |
224 | | 9:45am [[BR]] |
225 | | |
226 | | Ahmed El-Hassany (IU) [[BR]] |
227 | | |
228 | | Tasks [[BR]] |
229 | | * Continue Unified Network Information Service (UNIS), to provide combined Lookup and Topology Services, initially for use with GEMINI tool set. |
230 | | |
231 | | Summary |
232 | | * [wiki:InstMeasTopic_4.7LookupService status at GEC13] [[BR]] |
233 | | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/UNIS_GEC14.pdf UNIS configuration at GEC14; proposed configuration] [[BR]] |
234 | | |
235 | | Discussion |
236 | | * Who is lead? [[BR]] |
237 | | * Will you refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances? [[BR]] |
238 | | * What additional features are under consideration? [[BR]] |
239 | | * What new interfaces are under consideration? [[BR]] |
240 | | * Will the GIMI project want to use the UNIS service? [[BR]] |
241 | | * Will other parts of GENI want to use the UNIS service, e.g., stitching? [[BR]] |
242 | | * Do we need a breakout session for further discussion? when? [[BR]] |
| 78 | |
| 115 | |
| 116 | |
| 117 | |
| 118 | |
| 119 | |
| 120 | == GENI I&M Architecture and Tools: Goals, Overview and Status == |
| 121 | |
| 122 | * GIMI I&M tool set design [[BR]] |
| 123 | * Based on OML, provides basic host and active network measurements [[BR]] |
| 124 | * Ready for use on ExoGENI racks; successful tutorial [[BR]] |
| 125 | * Introduces XML messaging service, iRODS archive service, IREEL(lab wiki) portal service; use by others? iRODS by GEMINI [[BR]] |
| 126 | * Spiral 5 goals: also work with InstaGENI racks, WiMAX sites [[BR]] |
| 127 | |
| 128 | * GEMINI I&M tool set design [[BR]] |
| 129 | * Based on INSTOOLS and perfSONAR/LAMP, provides basic host and active network measurements [[BR]] |
| 130 | * Ready for use on InstaGENI/protoGENI racks ; successful tutorial [[BR]] |
| 131 | * Introduces portal to GUIs service, UNIS unified ntwk info service; use by others? [[BR]] |
| 132 | * Spiral 5 goals: also work with ExoGENI racks [[BR]] |
| 133 | |
| 134 | * Need simplified MDOD measurement data object descriptor schema [[BR]] |
| 135 | * Also service for creation and editing of MDOD [[BR]] |
| 136 | * Possible extensions to other GENI objects, events [[BR]] |
| 137 | |
| 138 | [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/071112%20I%26M%20GEC14%20Wrap-Up%20Agenda.ppt slides] [[BR]] |
| 139 | |
| 140 | |
| 141 | |
| 142 | === GIMI I&M Tools: Goals, Overview and Status === |
| 143 | |
| 144 | '''PI''' Michael Zink, University of Massachusetts at Amherst (mailto:zink@ecs.umass.edu) [[BR]] |
| 145 | '''Co-PI''' Max Ott, NICTA (mailto:max.ott@nicta.com.au) [[BR]] |
| 146 | '''Key personnel''' Ilia Baldine, RENCI (mailto:ibaldin@renci.org) [[BR]] |
| 147 | |
| 148 | [wiki:GIMI GIMI wiki] [[BR]] |
| 149 | [http://gimi.ecs.umass.edu/ GIMI website at UMass Amherst] [[BR]] |
| 150 | |
| 151 | Goals [[BR]] |
| 152 | * Starts with OML, and provides easy-to-use tools for GENI environment [[BR]] |
| 153 | |
| 154 | * First focus: I&M use cases for experiments, with default OML Client in nodes that gathers passive measurements like INSTOOLS, and provides basic node-to-node connectivity tests using ping and iperf [[BR]] |
| 155 | * Second focus: I&M use cases for infrastructure measurement [[BR]] |
| 156 | * Later focus: add sensor measurement data, carried in data network [[BR]] |
| 157 | |
| 158 | * Spiral 4 supported aggregates: ORCA servers/VMs and ExoGENI (RENCI) racks [[BR]] |
| 159 | * Later, support: WiMAX sites [[BR]] |
| 160 | * Spiral 5 supported aggregates: protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]] |
| 161 | |
| 162 | * Introduces XML messaging service, with pub/sub, in public IP space [[BR]] |
| 163 | * Introduces iRODS service, as a measurement data archive. [[BR]] |
| 164 | * Introduces IREEL portal service, for measurement data analysys and presentation. [[BR]] |
| 165 | |
| 166 | |
| 167 | Summary: [[BR]] |
| 168 | |
| 169 | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/GIMI%20GEC%2014%20I%26M%20Session.pptx GIMI architecture, design and status at GEC14; plan for GEC-14 tutorial; next steps during Spiral 5] [[BR]] |
| 170 | * For more information, attend or audit [http://groups.geni.net/geni/wiki/GIMIv1.0Tutorial GIMI v1.0 tutorial] [[BR]] |
| 171 | |
| 172 | |
| 173 | |
| 174 | === GEMINI I&M Tools: Goals, Overview and Status === |
| 175 | |
| 176 | '''PI''' Martin Swany, Indiana University (mailto:swany@iu.edu) [[BR]] |
| 177 | '''Co-PI''' Chris Small, Indiana University (mailto:chsmall@indiana.edu) [[BR]] |
| 178 | '''Co-PI''' James Griffioen, University of Kentucky (mailto:griff@netlab.uky.edu) [[BR]] |
| 179 | '''Co-PI''' Zongming Fei, University of Kentucky (mailto:fei@netlab.uky.edu) [[BR]] |
| 180 | |
| 181 | [wiki:GEMINI GEMINI wiki] [[BR]] |
| 182 | |
| 183 | Goals [[BR]] |
| 184 | |
| 185 | * Includes LAMP code and features in GEMINI tools, to provides flexible tools based on perfSONAR for active infrastructure measurements [[BR]] |
| 186 | * Includes INSTOOLS code and features in GEMINI tools, to gather basic host measurements [[BR]] |
| 187 | * Later, integrates LAMP and INSTOOLS code and features into new code base for GEMINI tools. [[BR]] |
| 188 | |
| 189 | * First focus: I&M use cases for infrastructure measurement [[BR]] |
| 190 | * Include sharing of data with other users (e.g., operators), at an interface with authorization using a GENI credential [[BR]] |
| 191 | * Show how to monitor clusters/racks [[BR]] |
| 192 | * Show how to measure Layer 2 and OpenFlow paths (with input from OnTimeMeasure project) [[BR]] |
| 193 | |
| 194 | * Second focus: I&M use cases for experiments [[BR]] |
| 195 | * Gather basic host measurements (as was done by INSTOOLS using SNMP) [[BR]] |
| 196 | * Show how to gather customized data from applications (as provided by OML Client) [[BR]] |
| 197 | |
| 198 | * Spiral 4 supported aggregates: protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]] |
| 199 | * Spiral 5 supported aggregates: ORCA servers/VMs and ExoGENI (RENCI) racks [[BR]] |
| 200 | |
| 201 | * Continues INSTOOLS portal service, to find GUIs [[BR]] |
| 202 | * Continues LAMP local and global Unified Network Information Service (UNIS), to register available measurement data, and network topology [[BR]] |
| 203 | |
| 204 | Summary [[BR]] |
| 205 | |
| 206 | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/GEMINI%20Overview%20and%20Direction-GEC14.pptx GEMINI architecture, design and status at GEC14; plan for GEC-14 tutorial; next steps during Spiral 5] [[BR]] |
| 207 | * For more information, attend or audit [http://groups.geni.net/geni/wiki/GEMINITutorial GEMINI v1.0 tutorial] [[BR]] |
| 208 | |
| 209 | |
| 210 | |
| 211 | |
| 212 | |
| 213 | == Persistent Multi-user I&M Services == |
| 214 | |
| 215 | |
| 216 | Goals [[BR]] |
| 217 | * Use by both GIMI and GEMINI tools sets [[BR]] |
| 218 | * Use by other parts of GENI [[BR]] |
| 219 | * Identify need for further reviews and discussions, in breakout meetings on Wed, 7/11 [[BR]] |
| 220 | |
| 221 | |
| 222 | === S1) XML Messaging Service === |
| 223 | |
| 224 | === S2) iRODS Service === |
| 225 | 9:15am [[BR]] |
| 226 | |
| 227 | Shu Huang (RENCI) [[BR]] |
| 228 | |
| 229 | Tasks |
| 230 | * Establish iRODS service(s), and define rules (interfaces) to provide GENI measurement data archive functions. [[BR]] |
| 231 | |
| 232 | Summary |
| 233 | * [wiki:InstMeasTopic_4.9ArchiveService status at GEC13] [[BR]] |
| 234 | * [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T9b%29%20%20gec13_irods_im_anirban.pptx slides at GEC13] [[BR]] |
| 235 | * iRODS service has been established at RENCI [[BR]] |
| 236 | * iRODS service has been established at Univ of Kentucky [[BR]] |
| 237 | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/irods-gec14-1.pptx iRODS configuration at GEC14] [[BR]] |
| 238 | * Proposed configuration? [[BR]] |
| 239 | * Operations plan? [[BR]] |
| 240 | |
| 241 | Discussion |
| 242 | * Who is lead? [[BR]] |
| 243 | * Will all iRODS services be federated, for redundancy? |
| 244 | * How to move data to service: move file; move SQL DB; or? [[BR]] |
| 245 | * How is persistent object identifier (i.e., handle) generated? also registered? and later resolved? Include necessary Object Identifier (OI) service.[[BR]] |
| 246 | * How are partitions for different users managed? [[BR]] |
| 247 | * How is authorization for a user done? [[BR]] |
| 248 | * How is data in MDOD used to set archive sharing policy? what is required in MDOD? [[BR]] |
| 249 | * How will the GEMINI project use the iRODS service? [[BR]] |
| 250 | * Will other parts of GENI want to use the iRODS service? [[BR]] |
| 251 | * Do we need a breakout session for further discussion? when? [[BR]] |
| 252 | |
| 253 | === S3) GIMI Portal Service === |
| 254 | 9:30am [[BR]] |
| 255 | |
| 256 | Max Ott and Christoph Dwertmann (NICTA); Mike Zink and Cong Wang (UMass Amherst) [[BR]] |
| 257 | |
| 258 | Tasks |
| 259 | * Establish IREEL service, to provide measurement analysis and presentation functions, starting with GIMI project [[BR]] |
| 260 | * Extend/change to become Lab wiki service [[BR]] |
| 261 | |
| 262 | Summary |
| 263 | * IREEL service has been established at NICTA [[BR]] |
| 264 | * IREEL service has been established at UMassAmherst [[BR]] |
| 265 | * Current configuration [ slides] [[BR]] |
| 266 | * Proposed configuration [ slides] [[BR]] |
| 267 | * Operations plan [ slides] [[BR]] |
| 268 | |
| 269 | Discussion |
| 270 | * Who is lead? [[BR]] |
| 271 | * How are partitions for different users managed? [[BR]] |
| 272 | * How is authorization for a user done? [[BR]] |
| 273 | * Can IREEL be used to provide other functions, e.g., experiment meangement? if so, how? [[BR]] |
| 274 | * Will the GEMINI project want to use the IREEL service? [[BR]] |
| 275 | * Will other parts of GENI want to use the IREEL service? [[BR]] |
| 276 | * Do we need a breakout session for further discussion? when? [[BR]] |
| 277 | |
| 278 | === S4) GEMINI portal-to-GUIs Service === |
| 279 | 9:40am [[BR]] |
| 280 | |
| 281 | Charles Carpenter (U Kentucky) [[BR]] |
| 282 | |
| 283 | Tasks: |
| 284 | * Continue INSTOOLS portal-to-GUIs service, to allow user to locate GUIs within their slice, for use with INSTOOLS and GEMINI tools [[BR]] |
| 285 | |
| 286 | Summary |
| 287 | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/GEMINI%20Portal.ppt current GEMINI portal service configuration] [[BR]] |
| 288 | |
| 289 | Discussion |
| 290 | * Who is lead? [[BR]] |
| 291 | * How are partitions for different users managed? [[BR]] |
| 292 | * How is authorization for a user done? [[BR]] |
| 293 | * What additional features are under consideration? [[BR]] |
| 294 | * Will the GIMI project want to use the INSTOOLS portal-to-GUIs service? [[BR]] |
| 295 | * Will other parts of GENI want to use the INSTOOLS portal-to-GUIs service? [[BR]] |
| 296 | * Do we need a breakout session for further discussion? when? [[BR]] |
| 297 | |
| 298 | === S5) UNIS Service === |
| 299 | 9:45am [[BR]] |
| 300 | |
| 301 | Ahmed El-Hassany (IU) [[BR]] |
| 302 | |
| 303 | Tasks [[BR]] |
| 304 | * Continue Unified Network Information Service (UNIS), to provide combined Lookup and Topology Services, initially for use with GEMINI tool set. |
| 305 | |
| 306 | Summary |
| 307 | * [wiki:InstMeasTopic_4.7LookupService status at GEC13] [[BR]] |
| 308 | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/UNIS_GEC14.pdf UNIS configuration at GEC14; proposed configuration] [[BR]] |
| 309 | |
| 310 | Discussion |
| 311 | * Who is lead? [[BR]] |
| 312 | * Will you refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances? [[BR]] |
| 313 | * What additional features are under consideration? [[BR]] |
| 314 | * What new interfaces are under consideration? [[BR]] |
| 315 | * Will the GIMI project want to use the UNIS service? [[BR]] |
| 316 | * Will other parts of GENI want to use the UNIS service, e.g., stitching? [[BR]] |
| 317 | * Do we need a breakout session for further discussion? when? [[BR]] |
| 318 | |