200 | | Define, prototype, demonstrate and operate a GENI XML Messaging service, starting at GEC13. [[BR]] |
201 | | Support use in GENI by many tools, starting with GIMI I&M tools, who will use it to exchange OMF messages. [[BR]] |
202 | | Define operations plan for XML Messaging service. [[BR]] |
| 200 | * Define, prototype, demonstrate and operate a GENI XML Messaging service, starting at GEC13. [[BR]] |
| 201 | * Support use in GENI by many tools, starting with GIMI I&M tools, who will use it to exchange OMF messages. [[BR]] |
| 202 | * Define operations plan for XML Messaging service. [[BR]] |
206 | | [wiki:InstMeasTopic_4.6MessagingService work in progress] [[BR]] |
207 | | An XMPP server is operational at Rutgers WINLAB (and other GENI wireless sites) for OMF messages. [[BR]] |
208 | | An XML messaging service has been prototyped by the IMF project. [ slides] (see also I&M and Monitoring session at GEC14) [[BR]] |
209 | | An XMPP server has been setup at UMass Amherst. [[BR]] |
210 | | Current configuration [ slides] [[BR]] |
211 | | Proposed configuration [ slides] [[BR]] |
212 | | Operations plan [ slides] [[BR]] |
| 206 | * [wiki:InstMeasTopic_4.6MessagingService work in progress] [[BR]] |
| 207 | * An XMPP server is operational at Rutgers WINLAB (and other GENI wireless sites) for OMF messages. [[BR]] |
| 208 | * An XML messaging service has been prototyped by the IMF project. [ slides] (see also I&M and Monitoring session at GEC14) [[BR]] |
| 209 | * An XMPP server has been setup at UMass Amherst. [[BR]] |
| 210 | * Current configuration [ slides] [[BR]] |
| 211 | * Proposed configuration [ slides] [[BR]] |
| 212 | * Operations plan [ slides] [[BR]] |
215 | | Who is lead? [[BR]] |
216 | | Where will XMPP servers be located? will they be fully federated? [[BR]] |
217 | | How do we set "topics" in XMPP servers to support OMF messages? [[BR]] |
218 | | Will these XMPP servers provide a generalized GENI XML messaging service? If so, what functions will be included? |
219 | | What authorization mechanisms will be required? [[BR]] |
220 | | Will the GEMINI project want to use the XML messaging service? [[BR]] |
221 | | Will other parts of GENI (e.g., monitoring) want to use the XML messaging service? [[BR]] |
222 | | Do we need a breakout session for further discussion? when? [[BR]] |
| 215 | * Who is lead? [[BR]] |
| 216 | * Where will XMPP servers be located? will they be fully federated? [[BR]] |
| 217 | * How do we set "topics" in XMPP servers to support OMF messages? [[BR]] |
| 218 | * Will these XMPP servers provide a generalized GENI XML messaging service? If so, what functions will be included? |
| 219 | * What authorization mechanisms will be required? [[BR]] |
| 220 | * Will the GEMINI project want to use the XML messaging service? [[BR]] |
| 221 | * Will other parts of GENI (e.g., monitoring) want to use the XML messaging service? [[BR]] |
| 222 | * Do we need a breakout session for further discussion? when? [[BR]] |
235 | | [wiki:InstMeasTopic_4.9ArchiveService Work in Progress] [[BR]] |
236 | | [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T9b%29%20%20gec13_irods_im_anirban.pptx slides] [[BR]] |
237 | | iRODS service has been established at RENCI [[BR]] |
238 | | iRODS service has been established at Univ of Kentucky [[BR]] |
239 | | Current configuration [ slides] [[BR]] |
240 | | Proposed configuration [ slides] [[BR]] |
241 | | Operations plan [ slides] [[BR]] |
242 | | |
243 | | Discussion |
244 | | Who is lead? [[BR]] |
245 | | Will all iRODS services be federated, for redundancy? |
246 | | How to move data to service: move file; move SQL DB; or? [[BR]] |
247 | | How is persistent object identifier (i.e., handle) generated? also registered? and later resolved? Include necessary Object Identifier (OI) service.[[BR]] |
248 | | How are partitions for different users managed? [[BR]] |
249 | | How is data in MDOD used to set archive sharing policy? what is required in MDOD? [[BR]] |
250 | | Will the GEMINI project want to use the iRODS service? [[BR]] |
251 | | Will other parts of GENI want to use the iRODS service? [[BR]] |
252 | | Do we need a breakout session for further discussion? when? [[BR]] |
| 235 | * [wiki:InstMeasTopic_4.9ArchiveService Work in Progress] [[BR]] |
| 236 | * [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T9b%29%20%20gec13_irods_im_anirban.pptx slides] [[BR]] |
| 237 | * iRODS service has been established at RENCI [[BR]] |
| 238 | * iRODS service has been established at Univ of Kentucky [[BR]] |
| 239 | * Current configuration [ slides] [[BR]] |
| 240 | * Proposed configuration [ slides] [[BR]] |
| 241 | * Operations plan [ slides] [[BR]] |
| 242 | |
| 243 | Discussion |
| 244 | * Who is lead? [[BR]] |
| 245 | * Will all iRODS services be federated, for redundancy? |
| 246 | * How to move data to service: move file; move SQL DB; or? [[BR]] |
| 247 | * How is persistent object identifier (i.e., handle) generated? also registered? and later resolved? Include necessary Object Identifier (OI) service.[[BR]] |
| 248 | * How are partitions for different users managed? [[BR]] |
| 249 | * How is data in MDOD used to set archive sharing policy? what is required in MDOD? [[BR]] |
| 250 | * Will the GEMINI project want to use the iRODS service? [[BR]] |
| 251 | * Will other parts of GENI want to use the iRODS service? [[BR]] |
| 252 | * Do we need a breakout session for further discussion? when? [[BR]] |
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 sued 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]] |
| 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]] |
287 | | Current configuration [ slides] [[BR]] |
288 | | Proposed configuration [ slides] [[BR]] |
289 | | Operations plan [ slides] [[BR]] |
290 | | |
291 | | Discussion |
292 | | Who is lead? [[BR]] |
293 | | How are partitions for different users managed? [[BR]] |
294 | | How is authorization for a user done? [[BR]] |
295 | | What additional features are under consideration? |
296 | | Will the GIMI project want to use the INSTOOLS portal-to-GUIs service? [[BR]] |
297 | | Will other parts of GENI want to use the INSTOOLS portal-to-GUIs service? [[BR]] |
298 | | Do we need a breakout session for further discussion? when? [[BR]] |
| 287 | * Current configuration [ slides] [[BR]] |
| 288 | * Proposed configuration [ slides] [[BR]] |
| 289 | * Operations plan [ slides] [[BR]] |
| 290 | |
| 291 | Discussion |
| 292 | * Who is lead? [[BR]] |
| 293 | * How are partitions for different users managed? [[BR]] |
| 294 | * How is authorization for a user done? [[BR]] |
| 295 | * What additional features are under consideration? [[BR]] |
| 296 | * Will the GIMI project want to use the INSTOOLS portal-to-GUIs service? [[BR]] |
| 297 | * Will other parts of GENI want to use the INSTOOLS portal-to-GUIs service? [[BR]] |
| 298 | * Do we need a breakout session for further discussion? when? [[BR]] |
309 | | [wiki:InstMeasTopic_4.7LookupService Work in Progress] [[BR]] |
310 | | Current configuration [ slides] [[BR]] |
311 | | Proposed configuration [ slides] [[BR]] |
312 | | Operations plan [ slides] [[BR]] |
313 | | |
314 | | Discussion |
315 | | Who is lead? [[BR]] |
316 | | Will you refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances? [[BR]] |
317 | | What additional features are under consideration? |
318 | | Will the GIMI project want to use the UNIS service? [[BR]] |
319 | | Will other parts of GENI want to use the UNIS service, e.g., stitching? [[BR]] |
320 | | Do we need a breakout session for further discussion? when? [[BR]] |
| 309 | * [wiki:InstMeasTopic_4.7LookupService Work in Progress] [[BR]] |
| 310 | * Current configuration [ slides] [[BR]] |
| 311 | * Proposed configuration [ slides] [[BR]] |
| 312 | * Operations plan [ slides] [[BR]] |
| 313 | |
| 314 | Discussion |
| 315 | * Who is lead? [[BR]] |
| 316 | * Will you refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances? [[BR]] |
| 317 | * What additional features are under consideration? [[BR]] |
| 318 | * Will the GIMI project want to use the UNIS service? [[BR]] |
| 319 | * Will other parts of GENI want to use the UNIS service, e.g., stitching? [[BR]] |
| 320 | * Do we need a breakout session for further discussion? when? [[BR]] |
329 | | Working and supported v1.0 GIMI tools should be available to users of ExoGENI racks [[BR]] |
330 | | Working and supported v1.0 GEMINI tools should be available to users of InstaGENI racks (and ProtoGENI/Emulab clusters) [[BR]] |
331 | | Tutorials for using both GIMI and GEMINI tool sets must be kept up-to-date, so that users can teach themselves [[BR]] |
332 | | Bugs must be gathered, tracked and fixed by GIMI and GEMINI teams; final acceptance test will be performed by the GPO [[BR]] |
333 | | Feature requests must be gathered, tracked and evaluated by GIMI and GEMINI teams [[BR]] |
334 | | |
335 | | v1.1 of GIMI tools must be released by GEC15, including bug fixes and new features, fully tested and ready for day-to-day use [[BR]] |
336 | | v1.1 of GEMINI tools must be released by GEC15, including bug fixes and new features, fully tested and ready for day-to-day use [[BR]] |
337 | | |
338 | | XML messaging service should provide agreed-upon features, and be reliably operational [[BR]] |
339 | | iRODS archive service should provide agreed-upon features, and be reliably operational [[BR]] |
340 | | IREEL analysis and presentation service should provide agreed-upon features, and be reliably operational [[BR]] |
341 | | INSTOOLS portal-to-GUIs service should provide agreed-upon features, and be reliably operational [[BR]] |
342 | | Unified Network Information Service (UNIS) should provide agreed-upon features, and be reliably operational [[BR]] |
343 | | |
344 | | |
345 | | Discussion |
346 | | Do we have leads identified for all items? [[BR]] |
347 | | How should user workspace be supported? on a VM? on a dedicated server? [[BR]] |
| 329 | * Working and supported v1.0 GIMI tools should be readily available to users of ExoGENI racks (who is lead?) [[BR]] |
| 330 | * Working and supported v1.0 GEMINI tools should be readily available to users of InstaGENI racks (and ProtoGENI/Emulab clusters) (who is lead?) [[BR]] |
| 331 | * Tutorial for GIMI tool set must be kept up-to-date, so that users can teach themselves (who is lead?) [[BR]] |
| 332 | * Tutorial for GEMINI tool set must be kept up-to-date, so that users can teach themselves (who is lead?) [[BR]] |
| 333 | * Bugs must be gathered, tracked and fixed by GIMI team; final acceptance test will be performed by the GPO (who is lead?) [[BR]] |
| 334 | * Bugs must be gathered, tracked and fixed by GEMINI team; final acceptance test will be performed by the GPO (who is lead?) [[BR]] |
| 335 | * Feature requests must be gathered, tracked and evaluated by GIMI and GEMINI team (who is lead?) [[BR]] |
| 336 | * Feature requests must be gathered, tracked and evaluated by GIMI and GEMINI team (who is lead?) [[BR]] |
| 337 | |
| 338 | * v1.1 of GIMI tools must be released by GEC15, including bug fixes and new features, fully tested and ready for day-to-day use (who is lead?) [[BR]] |
| 339 | * v1.1 of GEMINI tools must be released by GEC15, including bug fixes and new features, fully tested and ready for day-to-day use (who is lead?) [[BR]] |
| 340 | |
| 341 | * XML messaging service should provide agreed-upon features, and be reliably operational (who is lead?) [[BR]] |
| 342 | * iRODS archive service should provide agreed-upon features, and be reliably operational (who is lead?) [[BR]] |
| 343 | * IREEL analysis and presentation service should provide agreed-upon features, and be reliably operational (who is lead?) [[BR]] |
| 344 | * INSTOOLS portal-to-GUIs service should provide agreed-upon features, and be reliably operational (who is lead?) [[BR]] |
| 345 | * Unified Network Information Service (UNIS) should provide agreed-upon features, and be reliably operational (who is lead?) [[BR]] |
| 346 | |
| 347 | |
| 348 | Discussion |
| 349 | * Do we have leads identified for all items? [[BR]] |
| 350 | * How should user workspace be supported? on a VM? on a dedicated server? [[BR]] |