Changes between Version 17 and Version 18 of GEC12InstMeasWorkingSession


Ignore:
Timestamp:
10/28/11 08:59:45 (8 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC12InstMeasWorkingSession

    v17 v18  
    88== Description ==
    99
    10  This session will review the GENI I&M design and prototyping projects planned for Spiral 4 (this year), including the two large Solicitation 3 I&M D&P projects and those continuing projects from Solicitation 2.  Then, it will define and discuss the priority topics that must be resolved between now and GEC13.  [[BR]]
     10 This session will review the GENI I&M design and prototyping projects planned for Spiral 4 (this year), including the two large Solicitation 3 I&M D&P projects and those projects continuing from Solicitation 2.  Then, it will define and discuss the priority topics that must be resolved between now and GEC13.  [[BR]]
    1111
    1212== Summary ==
     
    2424Harry Mussman  [[BR]]
    2525
    26 === 2.1) New Sol 3 Projects ===
     26=== 2.1) Goals and Approach ===
     27
     28[  slides]  [[BR]]
     29
     30=== 2.2) New Sol 3 Projects ===
    2731
    2832GIMI [[BR]]
     
    3236Goals:  [[BR]]
    3337
    34 Starts with OML, and provides easy-to-use tools in GENI environment  [[BR]]
    35 
    36 First focus on I&M use cases for experiments, with default OML Client in nodes that gathers passive measurements like INSTOOLS  [[BR]]
    37 First supported aggregates:  ORCA servers/VMs and RENCI racks  [[BR]]
     38**Starts with OML, and provides easy-to-use tools for GENI environment  [[BR]]
     39
     40First focus: I&M use cases for experiments, with default OML Client in nodes that gathers passive measurements like INSTOOLS  [[BR]]
     41First supported aggregates:  ORCA servers/VMs and ExoGENI (RENCI) racks  [[BR]]
    3842First utilized experiment control tools:  GUSH, with additions  [[BR]]
    39 First utilized interfaces:  GENI AM API for resources;  ns3 for topology;  ssh;  add OMF for orchestration  [[BR]]
     43First utilized interfaces:  GENI AM API for resources;  ns3 for topology;  ssh;  OMF for orchestration  [[BR]]
    4044
    4145Requires XML messaging service, with pub/sub, in public IP space    [[BR]]
    4246
    43 Introduces portal service, with: OML Server, for collection; Results Service, for presentation; measurement orchestration service using OMF;  documentation service to create and edit MDOD.  Can this be shared with GEMINI project?  [[BR]]
    44 
    45 Introduces iRODS service for user workspace and archive.  Start with CNRI prototype?  Can GEMINI use iRODS?  Can iRODS serve as registry for MDOD?  [[BR]]
    46 
    47 Begin:  support for WiMAX sites  [[BR]]
    48 Consider:  adding OML server with perfSONAR interface, for sharing data [[BR]]
     47Introduces portal service, with: OML Server, for collection; Results Service, for presentation; measurement orchestration service using OMF;  documentation service to create and edit MDOD.  Can portal be shared with GEMINI project?  [[BR]]
     48
     49Introduces iRODS service for user workspace and archive.  Can GEMINI use iRODS?  Can iRODS serve as registry for MDOD?  [[BR]]
     50
     51Begin effort:  support for WiMAX sites  [[BR]]
     52Consider:  adding OML server with perfSONAR interface, for sharing data with GEMINI tools [[BR]]
    4953Later:  add sensor measurement data, carried in data network  [[BR]]
    5054
    5155GEMINI [[BR]]
    5256PI:  Martin Swany (Indiana U) [[BR]]
    53 Co-PI/Key:  Chris Small (Indiana U);  Eric Boyd (Internet2);  Jim Griffioen (U Kentucky);  Zongming Fei (U Kentucky) [[BR]]
     57Co-PI/Key:  Chris Small (Indiana U);  Eric Boyd (Internet2);  Jim Griffioen (U Kentucky);  Zongming Fei (U Kentucky) [[BR]];  Hussamuddin Nasir (U Kentucky)
    5458
    5559Goals:  [[BR]]
    5660
    57 Starts with INSTOOLS, and continues to provide easy-to-use tools in GENI environment  [[BR]]
     61**Starts with INSTOOLS, and continues to provide easy-to-use tools in GENI environment  [[BR]]
    5862Consider:  how to gather customized data from application  [[BR]]
    5963
    60 First focus on I&M use cases for experiments [[BR]]
     64First focus: I&M use cases for experiments [[BR]]
    6165First supported aggregates:  protoGENI servers/VMs;  can these be used for HP racks?  [[BR]]
    6266First utilized experiment control tools:  FLACK, with additions  [[BR]]
     
    6771Continues use of Kentucky and CNRI services for user workspace and archive.  Consider move to iRODS?  [[BR]]
    6872
    69 Starts with LAMP/perfSONAR, and continues to provide for infrastructure measurement, and for sharing of data  [[BR]]
     73**Starts with LAMP/perfSONAR, and continues to provide for infrastructure measurement, and for sharing of data  [[BR]]
    7074Continue to setup within resources assigned by slice mechanism [[BR]]
    7175Consider:  monitoring of clusters/racks [[BR]]
     
    8286Continue to use perfSONAR clients to present data;  can these be integrated into portal? [[BR]]
    8387
    84 Consider how INSTOOLS and LAMP/perfSONAR tools might be shared or merged   [[BR]]
     88**Consider how INSTOOLS and LAMP/perfSONAR tools might be shared or merged   [[BR]]
    8589
    8690
     
    9094LAMP/perfSONAR  [[BR]]
    9195PI:  Martin Swany (Indiana U)   [[BR]]   
    92 Co-PI/Key:  Eric Boyd (Internet2);  Jason Zurawski (Internet 2);  Guilherme Fernandes (U Delaware);  Ezra Kissel (U Delaware) [[BR]]
     96Co-PI/Key:  Eric Boyd (Internet2);  Jason Zurawski (Internet 2);  Guilherme Fernandes (U Delaware);  Ezra Kissel (U Delaware);  Mathew Jaffee (U Delaware) [[BR]]
    9397
    9498Goals:  [[BR]]
    9599
    96 Provides operational home and global Lookup Services  [[BR]]
     100**Demonstrate and/or help others to demonstrate “infrastructure measurement slices” in both protoGENI and ORCA environments, with the data available at the perfSONAR MP is  registered with the operational Lookup Service.  [[BR]]
     101
     102Provide operational home and global Lookup Services  [[BR]]
    97103Creates and maps MDOD into metadata that is registered in Lookup Service  [[BR]]
    98104
    99105Expand authorization at interface where data is shared;  introduce use of GENI credentials  [[BR]]
    100106
    101 Continue to participate in the GENI I&M effort, particularly in defining the schema for the “measurement data object descriptor”, and mapping it to the perfSONAR metadata that is registered with the Lookup Service.  [[BR]]
    102 
    103 Provide LAMP images for creating “infrastructure measurement slices” in both protoGENI and ORCA environments.  [[BR]]
    104 
    105 Install and operate a perfSONAR Lookup Service, for use with “infrastructure measurement slices”.  [[BR]]
    106 
    107 Demonstrate and/or help others to demonstrate “infrastructure measurement slices” in both protoGENI and ORCA environments, with the data available at the perfSONAR MP is  registered with the operational Lookup Service.  [[BR]]
    108 
    109 Demonstrate using GENI credentials to authorize access to the data available at the perfSONAR MP.  [[BR]]
    110 
    111 Define a plan for using ABAC to replace simple credentials to authorize the access to the data available at a perfSONAR MP.  [[BR]]
    112107
    113108
     
    118113Goals:
    119114
    120 Continue to participate in the GENI I&M effort, particularly in defining the schema for the “measurement data object descriptor”. [[BR]]
    121 
    122 Work with the LAMP project to understand the LAMP/perfSONAR tools, and demonstrate using them to implement “infrastructure measurement slices” in today’s GENI backbone and access networks. [[BR]]
     115**Work with the LAMP project to understand the LAMP/perfSONAR tools, and demonstrate using them to implement “infrastructure measurement slices” in today’s GENI backbone and access networks. [[BR]]
    123116
    124117Assuming LAMP/perfSONAR tools, develop a plan to evaluate the performance of today’s GENI IP backbone and access networks, using persistent or temporary “infrastructure measurement slices”, and utilizing existing perSONAR nodes in I2 and/or other networks. [[BR]]
     
    127120
    128121Define a procedure for evaluating the performance of GENI’s backbone and access networks when using OpenFlow (e.g., “Tango GENI”);  consider how to monitor the performance of OF networks, and introducing new specialized tools. [[BR]]
     122
    129123
    130124
    131125NetKarma  [[BR]]
    132126PI: Beth Plale (Indiana U) [[BR]]
    133 Co-PI/Key:  Chris Small (Indiana U); Scott Jensen (Indiana U) [[BR]]
     127Co-PI/Key:  Chris Small (Indiana U); Scott Jensen (Indiana U);  Mehmet Aktas (Indiana U) [[BR]]
    134128
    135129Goals:
    136130
    137 Participate in the GENI I&M effort, particularly in defining the schema for the “measurement data object descriptor”, and uses of “descriptors” in tracking provenance. [[BR]]
    138 
    139 Work with the GENI  I&M community to define extensions to the “descriptor” that would locate and describe objects beyond “measurement data objects” associated with an experiment, such as scripts, images, etc. [[BR]]
     131**Participate in defining the schema for the “measurement data object descriptor”, and uses of “descriptors” in tracking provenance. [[BR]]
     132
     133Work with the GENI community to define extensions to the “descriptor” that would locate and describe objects beyond “measurement data objects” associated with an experiment, such as scripts, images, etc. [[BR]]
    140134
    141135Modify your tools to create, gather and forward “descriptors”, that could locate and describe all objects associated with an experiment;  demonstrate how “descriptors” can be automatically created. [[BR]]
    142136
    143 
    144 Work with the GENI  I&M community to define a modified “descriptor” that would provide a standardized GENI “resource event record”;  these records could describe events such as assignments, faults or errors. [[BR]]
     137Work with the GENI I&M community to define a modified “descriptor” that would provide a standardized GENI “resource event record”;  these records could describe events such as assignments, faults or errors. [[BR]]
    145138
    146139Add modules to your tools to create, gather and forward “resource event records”, that when logged could fully describe the sequence of an experiment. [[BR]]
    147140 
    148 Demonstrate forwarding  your “records” using pub/sub servers and to repositories provided by the IMF project. [[BR]]
    149 
    150 Demonstrate your tools, and support experimenters in using them.  [[BR]]
    151 
    152 Participate in the GENI I&M effort, in fitting your provenance tools into the  “experimenter’s portal”.  [[BR]]
     141Work towards fitting your provenance tools into the  “experimenter’s portal”.  [[BR]]
    153142
    154143
     
    159148Goals:  [[BR]]
    160149
    161 Participate in the GENI I&M effort, focusing on providing basic capabilities, and on extending the architecture to include a pub/sub mechanism.  [[BR]]
    162 
    163 Prototype and demonstrate a GENI I&M capability to manage I&M services/slivers within a slice using a “measurement orchestration service”;  use ORBIT Management Framework (OMF) software modules provided by NICTA, including the Experiment Controller (EC) and the Resource Controller (RC), that communicate using a pub/sub mechanism utilizing an XMPP server.  [[BR]]
    164 
    165 Define and prototype an authorization mechanism for your sliver management service;  consider message signing being proposed by NICTA.  [[BR]]
    166 
    167 Demonstrate your capability to manage a sliver.  [[BR]]
    168 
    169 Prototype and demonstrate a GENI I&M capability to transport event (or measurement) records;  include software modules that collect the records, communicate using a pub/sub mechanism utilizing an XMPP server, archive the records in a repository, search the records, and display the records.  [[BR]]
    170 
    171 Define and prototype an authorization mechanism for your event record transport service.   [[BR]]
    172 
    173 Demonstrate your capability by transporting and distributing standardized GENI “resource event records”, as defined by the NetKarma project;  these records could describe events such as assignments, faults or errors.  [[BR]]
    174 
    175 Prototype and operate a GENI I&M service to provide pub/sub services utilizing an XMPP server, for use by your sliver management and event record transport services.  [[BR]]
    176 
    177 Define and prototype a resource assignment mechanism (using the GENI AM API, if possible) for users (experimenters and operators) to define nodes within your GENI pub/sub service, as they establish modules that publish or subscribe.  [[BR]]
    178 
    179 Prototype and operate a data repository associated with your pub/sub service, that could subscribe to a node and archive all event messages.  [[BR]]
     150**Prototype and operate a GENI XML messaging service, with pub/sub, based on an XMPP server and XCP-0060.  [[BR]]
     151
     152Prototype and demonstrate a GENI I&M “measurement orchestration service”, based on the ORBIT Management Framework (OMF) software modules provided by NICTA, including the Experiment Controller (EC) and the Resource Controller (RC).  [[BR]]
     153
     154Prototype and demonstrate using your pub/sub capability to transport and distribute standardized GENI “resource event records”, as defined by the NetKarma project.  [[BR]]
    180155
    181156
     
    186161Goals:  [[BR]]
    187162
    188 Continue to deploy a prototype Measurement Data Archive (MDA) service, and support integration with GENI I&M tools.  [[BR]]
    189 
    190 Participate in the GENI I&M effort, particularly in the MDA specification effort that includes defining metadata model for archived entities, defining access-control layer, and integrating control framework authorization scheme with the MDA.  [[BR]]
     163Continue to deploy a prototype Measurement Data Archive (MDA) service.  [[BR]]
     164
     165**Participate in the GENI I&M effort, particularly in the MDA specification effort that includes defining metadata model for archived entities, defining access-control layer, and integrating control framework authorization scheme with the MDA.  [[BR]]
    191166
    192167Enforce metadata schema on archived objects, and enable access control rights as defined by the MDA specification.  [[BR]]
    193 
    194 Integrate GENI identity management and authorization scheme if feasible and applicable, resources permitting.  [[BR]]
    195168
    196169Evangelize and demonstrate how the MDA/DOR service can be used to archive published data.  [[BR]]