Changes between Version 3 and Version 4 of GEC16Agenda/IMDesignTopics


Ignore:
Timestamp:
03/05/13 10:40:06 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC16Agenda/IMDesignTopics

    v3 v4  
    33= I&M Design Topics =
    44
    5 == Schedule ==
    6 
    7 Tuesday, 10:30am - noon
    8 
    9 == Session Leaders ==
    10 
    11 Harry Mussman.  GENI Project Office
    12 
    13 
    14 == Agenda / Details ==
    15 
    16 
    17 == 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 
    28 Tuesday, October 23, 8:30am - 10am [[BR]]
     5Tuesday, March 19, 10:30am - 12noon [[BR]]
    296Room:   [[BR]]
    307Session leader:  Harry Mussman (GENI Project Office, Raytheon BBN Technologies) [[BR]]
     
    3815Finally, we will discuss the I&M goals for the next 4 months, particularly how to best support experimenters and those doing infrastructure measurement. [[BR]]
    3916
     17== Pre-Requisites ==
     18
     19None  [[BR]]
     20
    4021== Agenda ==
    4122This is a tentative agenda, which may change. [[BR]]
     
    44258:30am [[BR]]
    4526
    46 == 2)  Topics for this meeting ==
    4727
    48 === T9)  GENI Storage and Archive Service (based on iRODS) ===
    49 8:35am [[BR]]
     28== 2) Meeting Introduction ==
     298:35am  [[BR]]
     30Harry Mussman  (GENI Project Office)  [[BR]]
    5031
    51 Shu Huang (RENCI) [[BR]]
     32Goals and Approach
     33 * Work towards a "unified experiment environment".
     34 * Help groups prepare responses to Sol 4
    5235
    53 Tasks
    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]]
     36Current overall experiment configuration 
    5837
    59 Design 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]]
     38Summary of current experiment steps
    6739
    68 Current implementation and next steps
     40Possible next steps towards a “unified experiment environment”.
    6941
    70  * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/IMDesignTopics/iRODS%20GENI%20plan.docx  iRODS GENI Plan]  [[BR]]
     42Today’s discussion topics:
     43 * Common graphical resource assignment tool
     44 * Rationalization of all graphical portals, and all graphical tools
     45 * Introduction of OMF to configure/orchestrate I&M and ExpApp services
    7146
    72 Open 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]]
    8347
    84 Team
    85  * Shu Huang (RENCI), GIMI project, Lead
    86  * ? , GEMINI project
    87  * Giridhar Manepalli (CNRI)
    88  * Harry Mussman and Jeanne Ohren (GPO)
    89  
     48
     49
     50
    9051
    9152
     
    210171
    211172
     173== 4)  Adjourn ==
     17412noon [[BR]]
    212175
    213 === T5)  Digital Objects, Identifiers and Descriptors  ===
    214 9:05am [[BR]]
    215 
    216 Giridhar Manepalli (CNRI) [[BR]]
    217 
    218 Tasks
    219  * 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).
    220  * 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
    221  
    222 Design goals
    223 
    224 Approach and next steps
    225 
    226  * [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/IMDesignTopics/MD_Workspace_And_Archive_GEC15.pptx  Archive, DOI (handle), Descriptors]  [[BR]]
    227 
    228 Open issues
    229 
    230 
    231 Team
    232  * Giridhar Manepalli and Larry Lannom (CNRI)
    233  * Harry Mussman and Jeanne Ohren (GPO)
    234  * ?, GIMI project
    235  * ?, GEMINI project
    236 
    237 
    238 === T10)  I&M Service-to-Service Authentication and Authorization  ===
    239 9:25am [[BR]]
    240 
    241 Ezra Kissel  (IU) [[BR]]
    242 
    243 
    244 Tasks
    245  * Establish a approach for providing authentication and authorization between GENI I&M service when they are required.
    246  * Note:  One approach included in LAMP tools from IU
    247  * Note:  Most authentication and authorization work in GENI has been focused on resource assignment, between an experimenter's tolls and an aggregate manager
    248  
    249 Design goals and approach
    250 
    251 Current implementation and next steps
    252 
    253  [http://groups.geni.net/geni/attachment/wiki/GEMINI/AA-workflow.png  GEMINI AA Workflow Configuration]  [[BR]]
    254  [http://groups.geni.net/geni/attachment/wiki/GEMINI/101112%20%20gemini_aa.txt  GEMINI AA Workflow Process]  [[BR]]
    255  [http://groups.geni.net/geni/attachment/wiki/GEMINI/092812b_gemini_aa_continued.txt  Status]  [[BR]]
    256  [http://groups.geni.net/geni/attachment/wiki/GEMINI/Visio-083112_AuthenticationAuthorization_Figures.pdf  AA Reference Configurations]  [[BR]]
    257  [http://groups.geni.net/geni/attachment/wiki/GEC15Agenda/IMDesignTopics/IM_AA.pptx  I&M A&A Considerations (slides)]  [[BR]]
    258 
    259 Open issues
    260 
    261 
    262 Team
    263  * Ezra Kissel (IU), GEMINI project, Lead
    264  * ?, GIMI project
    265  * Harry Mussman and Jeanne Ohren (GPO)
    266 
    267 
    268 == 3)  Goals for the next 4 months ==
    269 9:45am [[BR]]
    270 
    271 Harry Mussman  (GPO) [[BR]]
    272 
    273 Goals
    274  * Both GIMI and GEMINI tools should be available to Users during this period  [[BR]]
    275   * Acceptance testing continued by the GPO (Jeanne Ohren)  [[BR]]
    276   * Bug tracking system, plus periodic bug fixes, continued   (who are leads?)  [[BR]]
    277   * How can we facilitate feedback from Users, after EVERY use?  [[BR]]
    278 
    279  * Both GIMI and GEMINI must provide a high level of support to Users  [[BR]]
    280   * Tutorials must be kept up-to-date and operational, so that Users can teach themselves. (who are leads?)  [[BR]]
    281   * Instructions must be continuously refined, to make the tools easier to use. (who are leads?)  [[BR]]
    282   * Requested tool extensions must be gathered from users, based upon their experience. (who are leads?)  [[BR]]
    283   * Users with advanced requirements must be found, better identify gaps in the tools.  How? (who are leads?)  [[BR]]
    284   * Tool extensions must be proposed by the teams, and reviewed with the users.  How? (who are leads?)  [[BR]]
    285   * A list of tool extensions needs to be developed for inclusion into v1.1, due at GEC15. (who are leads?)  [[BR]]
    286 
    287  * Persistent multi-user services must be reliably available to all Users  [[BR]]
    288   * User Worksapce   (Jeanne Ohren)  [[BR]]
    289   * XML messaging service  (who is lead?)    [[BR]]
    290   * iRODS archive service   (who is lead?)  [[BR]]
    291   * IREEL analysis and presentation service    (who is lead?)  [[BR]]
    292   * INSTOOLS portal-to-GUIs service   (who is lead?)   [[BR]]
    293   * Unified Network Information Service (UNIS)   (who is lead?)  [[BR]]
    294 
    295 
    296 Discussion
    297  * Do we have leads identified for all items?  [[BR]]
    298 
    299 
    300 == 4)  Adjourn ==
    301 10:00am [[BR]]
    302 
    303 
    304 = I&M References =
    305 
    306 
    307 
    308 == GENI I&M Architecture and Tools:  Goals, Overview and Status ==
    309 
    310  * GIMI I&M tool set design [[BR]]
    311   * Based on OML, provides basic host and active network measurements [[BR]]
    312   * Ready for use on ExoGENI racks;  successful tutorial [[BR]]
    313   * Introduces XML messaging service, iRODS archive service, IREEL(lab wiki) portal service;  use by others?  iRODS by GEMINI [[BR]]
    314   * Spiral 5 goals:  also work with InstaGENI racks, WiMAX sites [[BR]]
    315 
    316  * GEMINI I&M tool set design [[BR]]
    317   * Based on INSTOOLS and perfSONAR/LAMP, provides basic host and active network measurements [[BR]]
    318   * Ready for use on InstaGENI/protoGENI racks ;  successful tutorial [[BR]]
    319   * Introduces portal to GUIs service, UNIS unified ntwk info service;  use by others?   [[BR]]
    320   * Spiral 5 goals:  also work with ExoGENI racks [[BR]]
    321 
    322  * Need simplified MDOD measurement data object descriptor schema [[BR]]
    323   * Also service for creation and editing of MDOD [[BR]]
    324   * Possible extensions to other GENI objects, events [[BR]]
    325 
    326  [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/071112%20I%26M%20GEC14%20Wrap-Up%20Agenda.ppt  slides]  [[BR]]
    327 
    328 
    329 
    330 === GIMI I&M Tools:  Goals, Overview and Status ===
    331 
    332 '''PI''' Michael Zink,  University of Massachusetts at Amherst  (mailto:zink@ecs.umass.edu)  [[BR]]
    333 '''Co-PI'''  Max Ott, NICTA  (mailto:max.ott@nicta.com.au) [[BR]]
    334 '''Key personnel''' Ilia Baldine, RENCI  (mailto:ibaldin@renci.org) [[BR]]
    335 
    336 [wiki:GIMI  GIMI wiki]  [[BR]]
    337 [http://gimi.ecs.umass.edu/  GIMI website at UMass Amherst]  [[BR]]
    338 
    339 Goals [[BR]]
    340  * Starts with OML, and provides easy-to-use tools for GENI environment  [[BR]]
    341 
    342  * 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]]
    343  * Second focus:  I&M use cases for infrastructure measurement  [[BR]]
    344  * Later focus:  add sensor measurement data, carried in data network  [[BR]]
    345 
    346  * Spiral 4 supported aggregates:  ORCA servers/VMs and ExoGENI (RENCI) racks  [[BR]]
    347  * Later, support:  WiMAX sites  [[BR]]
    348  * Spiral 5 supported aggregates:  protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]]
    349 
    350  * Introduces XML messaging service, with pub/sub, in public IP space    [[BR]]
    351  * Introduces iRODS service, as a measurement data archive.  [[BR]]
    352  * Introduces IREEL portal service, for measurement data analysys and presentation.  [[BR]]
    353 
    354 
    355 Summary:  [[BR]]
    356 
    357  * [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]]
    358  * For more information, attend or audit [http://groups.geni.net/geni/wiki/GIMIv1.0Tutorial  GIMI v1.0 tutorial]  [[BR]]
    359 
    360 
    361 
    362 === GEMINI I&M Tools:  Goals, Overview and Status ===
    363 
    364 '''PI''' Martin Swany, Indiana University  (mailto:swany@iu.edu) [[BR]]
    365 '''Co-PI'''  Chris Small,  Indiana University  (mailto:chsmall@indiana.edu) [[BR]]
    366 '''Co-PI''' James Griffioen,  University of Kentucky  (mailto:griff@netlab.uky.edu) [[BR]]
    367 '''Co-PI''' Zongming Fei,  University of Kentucky  (mailto:fei@netlab.uky.edu) [[BR]]
    368 
    369 [wiki:GEMINI  GEMINI wiki]  [[BR]]
    370 
    371 Goals  [[BR]]
    372 
    373  * Includes LAMP code and features in GEMINI tools, to provides flexible tools based on perfSONAR for active infrastructure measurements [[BR]]
    374  * Includes INSTOOLS code and features in GEMINI tools, to gather basic host measurements [[BR]]
    375  * Later, integrates LAMP and INSTOOLS code and features into new code base for GEMINI tools. [[BR]]
    376 
    377  * First focus:  I&M use cases for infrastructure measurement [[BR]]
    378  * Include sharing of data with other users (e.g., operators), at an interface with authorization using a GENI credential  [[BR]]
    379  * Show how to monitor clusters/racks [[BR]]
    380  * Show how to measure Layer 2 and OpenFlow paths (with input from OnTimeMeasure project) [[BR]]
    381 
    382  * Second focus: I&M use cases for experiments [[BR]]
    383  * Gather basic host measurements (as was done by INSTOOLS using SNMP) [[BR]]
    384  * Show how to gather customized data from applications (as provided by OML Client)  [[BR]]
    385 
    386  * Spiral 4 supported aggregates:  protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]]
    387  * Spiral 5 supported aggregates:  ORCA servers/VMs and ExoGENI (RENCI) racks  [[BR]]
    388 
    389  * Continues INSTOOLS portal service, to find GUIs    [[BR]]
    390  * Continues LAMP local and global Unified Network Information Service (UNIS), to register available measurement data, and network topology  [[BR]]
    391 
    392 Summary  [[BR]]
    393 
    394  * [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]]
    395  * For more information, attend or audit [http://groups.geni.net/geni/wiki/GEMINITutorial  GEMINI v1.0 tutorial]  [[BR]]
    396 
    397 
    398 
    399 
    400 
    401 == Persistent Multi-user I&M Services ==
    402 
    403 
    404 Goals  [[BR]]
    405  * Use by both GIMI and GEMINI tools sets [[BR]]
    406  * Use by other parts of GENI  [[BR]]
    407  * Identify need for further reviews and discussions  [[BR]]
    408 
    409 
    410 === S1)  GENI (XML) Messaging Service ===
    411 
    412 === S2)  GENI Storage and Archive Service (based on iRODS) ===
    413 9:15am [[BR]]
    414 
    415 Shu Huang (RENCI) [[BR]]
    416 
    417 Tasks
    418  * Establish iRODS service(s), and define rules (interfaces) to provide GENI measurement data archive functions.  [[BR]]
    419 
    420 Summary
    421  * [wiki:InstMeasTopic_4.9ArchiveService  status at GEC13]  [[BR]]
    422  * [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T9b%29%20%20gec13_irods_im_anirban.pptx  slides at GEC13]  [[BR]]
    423  * iRODS service has been established at RENCI  [[BR]]
    424  * iRODS service has been established at Univ of Kentucky  [[BR]]
    425  * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/irods-gec14-1.pptx  iRODS configuration at GEC14]   [[BR]]
    426  * Proposed configuration?  [[BR]]
    427  * Operations plan?  [[BR]]
    428 
    429 Discussion
    430  * Who is lead?  [[BR]]
    431  * Will all iRODS services be federated, for redundancy?
    432  * How to move data to service:  move file;  move SQL DB;  or? [[BR]]
    433  * How is persistent object identifier (i.e., handle) generated?  also registered?  and later resolved?  Include necessary Object Identifier (OI) service.[[BR]]
    434  * How are partitions for different users managed? [[BR]]
    435  * How is authorization for a user done?  [[BR]]
    436  * How is data in MDOD used to set archive sharing policy?  what is required in MDOD? [[BR]]
    437  * How will the GEMINI project use the iRODS service?  [[BR]]
    438  * Will other parts of GENI want to use the iRODS service?  [[BR]]
    439  * Do we need a breakout session for further discussion?  when?  [[BR]]
    440 
    441 === S3) GIMI Portal Service ===
    442 9:30am [[BR]]
    443 
    444 Max Ott and Christoph Dwertmann (NICTA);  Mike Zink and Cong Wang (UMass Amherst) [[BR]]
    445 
    446 Tasks
    447  * Establish IREEL service, to provide measurement analysis and presentation functions, starting with GIMI project  [[BR]]
    448  * Extend/change to become Lab wiki service  [[BR]]
    449 
    450 Summary
    451  * IREEL service has been established at NICTA [[BR]]
    452  * IREEL service has been established at UMassAmherst [[BR]]
    453  * Current configuration  [  slides]  [[BR]]
    454  * Proposed configuration [  slides]  [[BR]]
    455  * Operations plan  [  slides]  [[BR]]
    456 
    457 Discussion
    458  * Who is lead?  [[BR]]
    459  * How are partitions for different users managed? [[BR]]
    460  * How is authorization for a user done? [[BR]]
    461  * Can IREEL be used to provide other functions, e.g., experiment meangement?  if so, how?   [[BR]]
    462  * Will the GEMINI project want to use the IREEL service?  [[BR]]
    463  * Will other parts of GENI want to use the IREEL service?  [[BR]]
    464  * Do we need a breakout session for further discussion?  when?  [[BR]]
    465 
    466 === S4)  GEMINI Portal Service ===
    467 9:40am [[BR]]
    468 
    469 Charles Carpenter (U Kentucky) [[BR]]
    470 
    471 Tasks:
    472  * Continue INSTOOLS portal-to-GUIs service, to allow user to locate GUIs within their slice, for use with INSTOOLS and GEMINI tools [[BR]]
    473 
    474 Summary
    475  * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/GEMINI%20Portal.ppt  current GEMINI portal service configuration]  [[BR]]
    476 
    477 Discussion
    478  * Who is lead?  [[BR]]
    479  * How are partitions for different users managed? [[BR]]
    480  * How is authorization for a user done? [[BR]]
    481  * What additional features are under consideration?  [[BR]]
    482  * Will the GIMI project want to use the INSTOOLS portal-to-GUIs service?  [[BR]]
    483  * Will other parts of GENI want to use the INSTOOLS portal-to-GUIs service?  [[BR]]
    484  * Do we need a breakout session for further discussion?  when?  [[BR]]
    485 
    486 === S5) Unified Network Information Service (UNIS) ===
    487 9:45am  [[BR]]
    488 
    489 Ahmed El-Hassany (IU)  [[BR]]
    490 
    491 Tasks   [[BR]]
    492  * Continue Unified Network Information Service (UNIS), to provide combined Lookup and Topology Services, initially for use with GEMINI tool set.
    493 
    494 Summary
    495  * [wiki:InstMeasTopic_4.7LookupService  status at GEC13]  [[BR]]
    496  * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/UNIS_GEC14.pdf  UNIS configuration at GEC14;  proposed configuration]  [[BR]]
    497 
    498 Discussion
    499  * Who is lead?  [[BR]]
    500  * Will you refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances? [[BR]]
    501  * What additional features are under consideration?  [[BR]]
    502  * What new interfaces are under consideration?  [[BR]]
    503  * Will the GIMI project want to use the UNIS service?  [[BR]]
    504  * Will other parts of GENI want to use the UNIS service, e.g., stitching?  [[BR]]
    505  * Do we need a breakout session for further discussion?  when?  [[BR]]