Changes between Version 1 and Version 2 of GEC16Agenda/IMDesignTopics


Ignore:
Timestamp:
03/04/13 12:26:45 (6 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC16Agenda/IMDesignTopics

    v1 v2  
    1616
    1717== Pre-Requisites ==
     18
     19
     20
     21
     22
     23
     24[[PageOutline]]
     25
     26= Instrumentation and Measurement (I&M):  GIMI and GEMINI Design Topics at GEC15 =
     27
     28Tuesday, October 23, 8:30am - 10am [[BR]]
     29Room:   [[BR]]
     30Session leader:  Harry Mussman (GENI Project Office, Raytheon BBN Technologies) [[BR]]
     31
     32== Description ==
     33
     34This I&M session will focus on the key issues of interest to both the GIMI and GEMINI projects, as they continue to work towards a comprehensive set of I&M tools for GENI experimenters and for infrastructure measurement. In particular, we will consider the services and functions that can be used by both the GIMI and GEMINI projects.[[BR]]
     35
     36We will form teams that can resolve these issues.  [[BR]]
     37
     38Finally, we will discuss the I&M goals for the next 4 months, particularly how to best support experimenters and those doing infrastructure measurement. [[BR]]
     39
     40== Agenda ==
     41This is a tentative agenda, which may change. [[BR]]
     42
     43== 1)  Introductions ==
     448:30am [[BR]]
     45
     46== 2)  Topics for this meeting ==
     47
     48=== T9)  GENI Storage and Archive Service (based on iRODS) ===
     498:35am [[BR]]
     50
     51Shu Huang (RENCI) [[BR]]
     52
     53Tasks
     54 * Design and deploy GENI Storage and Archive Service for use by all GENI services.
     55 * Provide functions similar to the Measurement Data Archive (MDA) service prototype, designed by CNRI.
     56 * Use to store all types of experiment artifacts (not just measurement data), and identify objects to be moved to a long-term archive.
     57 * Implement using the iRODS data grid service, by defining rules (interfaces) to provide the necessary GENI functions.  [[BR]]
     58
     59Design goals and approach
     60 * [wiki:InstMeasTopic_4.9ArchiveService  status at GEC13]  [[BR]]
     61 * [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T9b%29%20%20gec13_irods_im_anirban.pptx  slides at GEC13]  [[BR]]
     62 * iRODS service has been established at RENCI  [[BR]]
     63 * iRODS service has been established at Univ of Kentucky  [[BR]]
     64 * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/irods-gec14-1.pptx  iRODS configuration at GEC14]   [[BR]]
     65 * Proposed configuration?  [[BR]]
     66 * Operations plan?  [[BR]]
     67
     68Current implementation and next steps
     69
     70 * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/IMDesignTopics/iRODS%20GENI%20plan.docx  iRODS GENI Plan]  [[BR]]
     71
     72Open issues
     73 * Who is lead?  [[BR]]
     74 * Will all iRODS services be federated, for redundancy?
     75 * How to move data to service:  move file;  move SQL DB;  or? [[BR]]
     76 * How is persistent object identifier (i.e., handle) generated?  also registered?  and later resolved?  Include necessary Object Identifier (OI) service.[[BR]]
     77 * How are partitions for different users managed? [[BR]]
     78 * How is authorization for a user done?  [[BR]]
     79 * How is data in MDOD used to set archive sharing policy?  what is required in MDOD? [[BR]]
     80 * How will the GEMINI project use the iRODS service?  [[BR]]
     81 * Will other parts of GENI want to use the iRODS service?  [[BR]]
     82 * Do we need a breakout session for further discussion?  when?  [[BR]]
     83
     84Team
     85 * Shu Huang (RENCI), GIMI project, Lead
     86 * ? , GEMINI project
     87 * Giridhar Manepalli (CNRI)
     88 * Harry Mussman and Jeanne Ohren (GPO)
     89 
     90
     91=== T5)  Digital Objects, Identifiers and Descriptors  ===
     929:05am [[BR]]
     93
     94Giridhar Manepalli (CNRI) [[BR]]
     95
     96Tasks
     97 * Define a comprehensive system for identifying and describing a wide range of digital objects, including all types of experiment artifacts (e.g., rspecs, scripts, measurement data).
     98 * Show how to group objects into one combined object (e.g., all artifacts associated with one experiment), and then identify, describe adn archive this combined object
     99 
     100Design goals
     101
     102Approach and next steps
     103
     104 * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/IMDesignTopics/MD_Workspace_And_Archive_GEC15.pptx  Archive, DOI (handle), Descriptors]  [[BR]]
     105
     106Open issues
     107
     108
     109Team
     110 * Giridhar Manepalli and Larry Lannom (CNRI)
     111 * Harry Mussman and Jeanne Ohren (GPO)
     112 * ?, GIMI project
     113 * ?, GEMINI project
     114
     115
     116=== T10)  I&M Service-to-Service Authentication and Authorization  ===
     1179:25am [[BR]]
     118
     119Ezra Kissel  (IU) [[BR]]
     120
     121
     122Tasks
     123 * Establish a approach for providing authentication and authorization between GENI I&M service when they are required.
     124 * Note:  One approach included in LAMP tools from IU
     125 * Note:  Most authentication and authorization work in GENI has been focused on resource assignment, between an experimenter's tolls and an aggregate manager
     126 
     127Design goals and approach
     128
     129Current implementation and next steps
     130
     131 [http://groups.geni.net/geni/attachment/wiki/GEMINI/AA-workflow.png  GEMINI AA Workflow Configuration]  [[BR]]
     132 [http://groups.geni.net/geni/attachment/wiki/GEMINI/101112%20%20gemini_aa.txt  GEMINI AA Workflow Process]  [[BR]]
     133 [http://groups.geni.net/geni/attachment/wiki/GEMINI/092812b_gemini_aa_continued.txt  Status]  [[BR]]
     134 [http://groups.geni.net/geni/attachment/wiki/GEMINI/Visio-083112_AuthenticationAuthorization_Figures.pdf  AA Reference Configurations]  [[BR]]
     135 [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/IMDesignTopics/IM_AA.pptx  I&M A&A Considerations (slides)]  [[BR]]
     136
     137Open issues
     138
     139
     140Team
     141 * Ezra Kissel (IU), GEMINI project, Lead
     142 * ?, GIMI project
     143 * Harry Mussman and Jeanne Ohren (GPO)
     144
     145
     146== 3)  Goals for the next 4 months ==
     1479:45am [[BR]]
     148
     149Harry Mussman  (GPO) [[BR]]
     150
     151Goals
     152 * Both GIMI and GEMINI tools should be available to Users during this period  [[BR]]
     153  * Acceptance testing continued by the GPO (Jeanne Ohren)  [[BR]]
     154  * Bug tracking system, plus periodic bug fixes, continued   (who are leads?)  [[BR]]
     155  * How can we facilitate feedback from Users, after EVERY use?  [[BR]]
     156
     157 * Both GIMI and GEMINI must provide a high level of support to Users  [[BR]]
     158  * Tutorials must be kept up-to-date and operational, so that Users can teach themselves. (who are leads?)  [[BR]]
     159  * Instructions must be continuously refined, to make the tools easier to use. (who are leads?)  [[BR]]
     160  * Requested tool extensions must be gathered from users, based upon their experience. (who are leads?)  [[BR]]
     161  * Users with advanced requirements must be found, better identify gaps in the tools.  How? (who are leads?)  [[BR]]
     162  * Tool extensions must be proposed by the teams, and reviewed with the users.  How? (who are leads?)  [[BR]]
     163  * A list of tool extensions needs to be developed for inclusion into v1.1, due at GEC15. (who are leads?)  [[BR]]
     164
     165 * Persistent multi-user services must be reliably available to all Users  [[BR]]
     166  * User Worksapce   (Jeanne Ohren)  [[BR]]
     167  * XML messaging service  (who is lead?)    [[BR]]
     168  * iRODS archive service   (who is lead?)  [[BR]]
     169  * IREEL analysis and presentation service    (who is lead?)  [[BR]]
     170  * INSTOOLS portal-to-GUIs service   (who is lead?)   [[BR]]
     171  * Unified Network Information Service (UNIS)   (who is lead?)  [[BR]]
     172
     173
     174Discussion
     175 * Do we have leads identified for all items?  [[BR]]
     176
     177
     178== 4)  Adjourn ==
     17910:00am [[BR]]
     180
     181
     182= I&M References =
     183
     184
     185
     186== GENI I&M Architecture and Tools:  Goals, Overview and Status ==
     187
     188 * GIMI I&M tool set design [[BR]]
     189  * Based on OML, provides basic host and active network measurements [[BR]]
     190  * Ready for use on ExoGENI racks;  successful tutorial [[BR]]
     191  * Introduces XML messaging service, iRODS archive service, IREEL(lab wiki) portal service;  use by others?  iRODS by GEMINI [[BR]]
     192  * Spiral 5 goals:  also work with InstaGENI racks, WiMAX sites [[BR]]
     193
     194 * GEMINI I&M tool set design [[BR]]
     195  * Based on INSTOOLS and perfSONAR/LAMP, provides basic host and active network measurements [[BR]]
     196  * Ready for use on InstaGENI/protoGENI racks ;  successful tutorial [[BR]]
     197  * Introduces portal to GUIs service, UNIS unified ntwk info service;  use by others?   [[BR]]
     198  * Spiral 5 goals:  also work with ExoGENI racks [[BR]]
     199
     200 * Need simplified MDOD measurement data object descriptor schema [[BR]]
     201  * Also service for creation and editing of MDOD [[BR]]
     202  * Possible extensions to other GENI objects, events [[BR]]
     203
     204 [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/071112%20I%26M%20GEC14%20Wrap-Up%20Agenda.ppt  slides]  [[BR]]
     205
     206
     207
     208=== GIMI I&M Tools:  Goals, Overview and Status ===
     209
     210'''PI''' Michael Zink,  University of Massachusetts at Amherst  (mailto:zink@ecs.umass.edu)  [[BR]]
     211'''Co-PI'''  Max Ott, NICTA  (mailto:max.ott@nicta.com.au) [[BR]]
     212'''Key personnel''' Ilia Baldine, RENCI  (mailto:ibaldin@renci.org) [[BR]]
     213
     214[wiki:GIMI  GIMI wiki]  [[BR]]
     215[http://gimi.ecs.umass.edu/  GIMI website at UMass Amherst]  [[BR]]
     216
     217Goals [[BR]]
     218 * Starts with OML, and provides easy-to-use tools for GENI environment  [[BR]]
     219
     220 * 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]]
     221 * Second focus:  I&M use cases for infrastructure measurement  [[BR]]
     222 * Later focus:  add sensor measurement data, carried in data network  [[BR]]
     223
     224 * Spiral 4 supported aggregates:  ORCA servers/VMs and ExoGENI (RENCI) racks  [[BR]]
     225 * Later, support:  WiMAX sites  [[BR]]
     226 * Spiral 5 supported aggregates:  protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]]
     227
     228 * Introduces XML messaging service, with pub/sub, in public IP space    [[BR]]
     229 * Introduces iRODS service, as a measurement data archive.  [[BR]]
     230 * Introduces IREEL portal service, for measurement data analysys and presentation.  [[BR]]
     231
     232
     233Summary:  [[BR]]
     234
     235 * [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]]
     236 * For more information, attend or audit [http://groups.geni.net/geni/wiki/GIMIv1.0Tutorial  GIMI v1.0 tutorial]  [[BR]]
     237
     238
     239
     240=== GEMINI I&M Tools:  Goals, Overview and Status ===
     241
     242'''PI''' Martin Swany, Indiana University  (mailto:swany@iu.edu) [[BR]]
     243'''Co-PI'''  Chris Small,  Indiana University  (mailto:chsmall@indiana.edu) [[BR]]
     244'''Co-PI''' James Griffioen,  University of Kentucky  (mailto:griff@netlab.uky.edu) [[BR]]
     245'''Co-PI''' Zongming Fei,  University of Kentucky  (mailto:fei@netlab.uky.edu) [[BR]]
     246
     247[wiki:GEMINI  GEMINI wiki]  [[BR]]
     248
     249Goals  [[BR]]
     250
     251 * Includes LAMP code and features in GEMINI tools, to provides flexible tools based on perfSONAR for active infrastructure measurements [[BR]]
     252 * Includes INSTOOLS code and features in GEMINI tools, to gather basic host measurements [[BR]]
     253 * Later, integrates LAMP and INSTOOLS code and features into new code base for GEMINI tools. [[BR]]
     254
     255 * First focus:  I&M use cases for infrastructure measurement [[BR]]
     256 * Include sharing of data with other users (e.g., operators), at an interface with authorization using a GENI credential  [[BR]]
     257 * Show how to monitor clusters/racks [[BR]]
     258 * Show how to measure Layer 2 and OpenFlow paths (with input from OnTimeMeasure project) [[BR]]
     259
     260 * Second focus: I&M use cases for experiments [[BR]]
     261 * Gather basic host measurements (as was done by INSTOOLS using SNMP) [[BR]]
     262 * Show how to gather customized data from applications (as provided by OML Client)  [[BR]]
     263
     264 * Spiral 4 supported aggregates:  protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]]
     265 * Spiral 5 supported aggregates:  ORCA servers/VMs and ExoGENI (RENCI) racks  [[BR]]
     266
     267 * Continues INSTOOLS portal service, to find GUIs    [[BR]]
     268 * Continues LAMP local and global Unified Network Information Service (UNIS), to register available measurement data, and network topology  [[BR]]
     269
     270Summary  [[BR]]
     271
     272 * [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]]
     273 * For more information, attend or audit [http://groups.geni.net/geni/wiki/GEMINITutorial  GEMINI v1.0 tutorial]  [[BR]]
     274
     275
     276
     277
     278
     279== Persistent Multi-user I&M Services ==
     280
     281
     282Goals  [[BR]]
     283 * Use by both GIMI and GEMINI tools sets [[BR]]
     284 * Use by other parts of GENI  [[BR]]
     285 * Identify need for further reviews and discussions  [[BR]]
     286
     287
     288=== S1)  GENI (XML) Messaging Service ===
     289
     290=== S2)  GENI Storage and Archive Service (based on iRODS) ===
     2919:15am [[BR]]
     292
     293Shu Huang (RENCI) [[BR]]
     294
     295Tasks
     296 * Establish iRODS service(s), and define rules (interfaces) to provide GENI measurement data archive functions.  [[BR]]
     297
     298Summary
     299 * [wiki:InstMeasTopic_4.9ArchiveService  status at GEC13]  [[BR]]
     300 * [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T9b%29%20%20gec13_irods_im_anirban.pptx  slides at GEC13]  [[BR]]
     301 * iRODS service has been established at RENCI  [[BR]]
     302 * iRODS service has been established at Univ of Kentucky  [[BR]]
     303 * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/irods-gec14-1.pptx  iRODS configuration at GEC14]   [[BR]]
     304 * Proposed configuration?  [[BR]]
     305 * Operations plan?  [[BR]]
     306
     307Discussion
     308 * Who is lead?  [[BR]]
     309 * Will all iRODS services be federated, for redundancy?
     310 * How to move data to service:  move file;  move SQL DB;  or? [[BR]]
     311 * How is persistent object identifier (i.e., handle) generated?  also registered?  and later resolved?  Include necessary Object Identifier (OI) service.[[BR]]
     312 * How are partitions for different users managed? [[BR]]
     313 * How is authorization for a user done?  [[BR]]
     314 * How is data in MDOD used to set archive sharing policy?  what is required in MDOD? [[BR]]
     315 * How will the GEMINI project use the iRODS service?  [[BR]]
     316 * Will other parts of GENI want to use the iRODS service?  [[BR]]
     317 * Do we need a breakout session for further discussion?  when?  [[BR]]
     318
     319=== S3) GIMI Portal Service ===
     3209:30am [[BR]]
     321
     322Max Ott and Christoph Dwertmann (NICTA);  Mike Zink and Cong Wang (UMass Amherst) [[BR]]
     323
     324Tasks
     325 * Establish IREEL service, to provide measurement analysis and presentation functions, starting with GIMI project  [[BR]]
     326 * Extend/change to become Lab wiki service  [[BR]]
     327
     328Summary
     329 * IREEL service has been established at NICTA [[BR]]
     330 * IREEL service has been established at UMassAmherst [[BR]]
     331 * Current configuration  [  slides]  [[BR]]
     332 * Proposed configuration [  slides]  [[BR]]
     333 * Operations plan  [  slides]  [[BR]]
     334
     335Discussion
     336 * Who is lead?  [[BR]]
     337 * How are partitions for different users managed? [[BR]]
     338 * How is authorization for a user done? [[BR]]
     339 * Can IREEL be used to provide other functions, e.g., experiment meangement?  if so, how?   [[BR]]
     340 * Will the GEMINI project want to use the IREEL service?  [[BR]]
     341 * Will other parts of GENI want to use the IREEL service?  [[BR]]
     342 * Do we need a breakout session for further discussion?  when?  [[BR]]
     343
     344=== S4)  GEMINI Portal Service ===
     3459:40am [[BR]]
     346
     347Charles Carpenter (U Kentucky) [[BR]]
     348
     349Tasks:
     350 * Continue INSTOOLS portal-to-GUIs service, to allow user to locate GUIs within their slice, for use with INSTOOLS and GEMINI tools [[BR]]
     351
     352Summary
     353 * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/GEMINI%20Portal.ppt  current GEMINI portal service configuration]  [[BR]]
     354
     355Discussion
     356 * Who is lead?  [[BR]]
     357 * How are partitions for different users managed? [[BR]]
     358 * How is authorization for a user done? [[BR]]
     359 * What additional features are under consideration?  [[BR]]
     360 * Will the GIMI project want to use the INSTOOLS portal-to-GUIs service?  [[BR]]
     361 * Will other parts of GENI want to use the INSTOOLS portal-to-GUIs service?  [[BR]]
     362 * Do we need a breakout session for further discussion?  when?  [[BR]]
     363
     364=== S5) Unified Network Information Service (UNIS) ===
     3659:45am  [[BR]]
     366
     367Ahmed El-Hassany (IU)  [[BR]]
     368
     369Tasks   [[BR]]
     370 * Continue Unified Network Information Service (UNIS), to provide combined Lookup and Topology Services, initially for use with GEMINI tool set.
     371
     372Summary
     373 * [wiki:InstMeasTopic_4.7LookupService  status at GEC13]  [[BR]]
     374 * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/UNIS_GEC14.pdf  UNIS configuration at GEC14;  proposed configuration]  [[BR]]
     375
     376Discussion
     377 * Who is lead?  [[BR]]
     378 * Will you refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances? [[BR]]
     379 * What additional features are under consideration?  [[BR]]
     380 * What new interfaces are under consideration?  [[BR]]
     381 * Will the GIMI project want to use the UNIS service?  [[BR]]
     382 * Will other parts of GENI want to use the UNIS service, e.g., stitching?  [[BR]]
     383 * Do we need a breakout session for further discussion?  when?  [[BR]]