Changes between Version 33 and Version 34 of GEC12InstMeasWorkingSession


Ignore:
Timestamp:
11/02/11 08:13:03 (9 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC12InstMeasWorkingSession

    v33 v34  
    2525
    2626Goals:
    27 
    28 Approach:
     27**Provide broad data gathering, analysis and archival capability that is sufficient for scientific mission, operations, and success of the infrastructure.
     28
     29**Remove the burden on researcher to become a system and network measurement infrastructure expert so that researcher can better focus on the science in the experiments
     30
     31**Follow defined I&M architecture
     32 
     33Approach:
     34** Two large I&M projects (GIMI and GEMINI) approved from Sol 3, which include groups that have provided OML, INSTOOLS and LAMP/perfSONAR tools
     35
     36**SOWS for remaining Year 3 of Sol 2 I&M projects focused on key topics that need to be resolved
     37
     38Architecture:
    2939
    3040Figure 1    GENI I&M Services and Messages [[BR]]
     
    4858**Starts with OML, and provides easy-to-use tools for GENI environment  [[BR]]
    4959
    50 First focus: I&M use cases for experiments, with default OML Client in nodes that gathers passive measurements like INSTOOLS  [[BR]]
     60*First focus: I&M use cases for experiments, with default OML Client in nodes that gathers passive measurements like INSTOOLS  [[BR]]
    5161First supported aggregates:  ORCA servers/VMs and ExoGENI (RENCI) racks  [[BR]]
    5262First utilized experiment control tools:  GUSH, with additions  [[BR]]
    5363First utilized interfaces:  GENI AM API for resources;  ns3 for topology;  ssh;  OMF for orchestration  [[BR]]
    5464
    55 Requires XML messaging service, with pub/sub, in public IP space    [[BR]]
    56 
    57 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 portal be shared with GEMINI project?  [[BR]]
    58 
    59 Introduces iRODS service for user workspace and archive.  Can GEMINI use iRODS?  Can iRODS serve as registry for MDOD?  [[BR]]
     65*Requires XML messaging service, with pub/sub, in public IP space    [[BR]]
     66
     67*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 portal be shared with GEMINI project?  [[BR]]
     68
     69*Introduces iRODS service for user workspace and archive.  Can GEMINI use iRODS?  Can iRODS serve as registry for MDOD?  [[BR]]
    6070
    6171Begin effort:  support for WiMAX sites  [[BR]]
     
    7787First utilized interfaces:  protoGENI API for resources;  ns3 for topology;  ssh;  [[BR]]
    7888
    79 Continues portal to presentation service;  need to add documentation service to create and edit MDOD.  Can portal be shared with GIMI project?  [[BR]]
    80 
    81 Continues use of Kentucky and CNRI services for user workspace and archive.  Consider move to iRODS?  [[BR]]
     89*Continues portal to presentation service;  need to add documentation service to create and edit MDOD.  Can portal be shared with GIMI project?  [[BR]]
     90
     91*Continues use of Kentucky and CNRI services for user workspace and archive.  Consider move to iRODS?  [[BR]]
    8292
    8393**Starts with LAMP/perfSONAR, and continues to provide for infrastructure measurement, and for sharing of data  [[BR]]
     
    91101First utilized interfaces:  protoGENI API for resources;  ns3 for topology;  ssh;  [[BR]]
    92102
    93 Continues home and global Lookup Services [[BR]]
     103*Continues home and global Lookup Services [[BR]]
    94104Create and map MDOD into metadata that is registered [[BR]]
    95105
    96 Continue to use perfSONAR clients to present data;  can these be integrated into portal? [[BR]]
    97 
    98 **Consider how INSTOOLS and LAMP/perfSONAR tools might be shared or merged   [[BR]]
     106*Continue to use perfSONAR clients to present data;  can these be integrated into portal? [[BR]]
     107
     108**Consider how INSTOOLS and LAMP/perfSONAR tools might be merged   [[BR]]
    99109
    100110
     
    110120**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]]
    111121
    112 Provide operational home and global Lookup Services  [[BR]]
    113 Creates and maps MDOD into metadata that is registered in Lookup Service  [[BR]]
    114 
    115 Expand authorization at interface where data is shared;  introduce use of GENI credentials  [[BR]]
     122*Provide operational home and global Lookup Services  [[BR]]
     123*Creates and maps MDOD into metadata that is registered in Lookup Service  [[BR]]
     124
     125*Expand authorization at interface where data is shared;  introduce use of GENI credentials  [[BR]]
    116126
    117127
     
    125135**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]]
    126136
    127 Assuming 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]]
    128 
    129 Define a procedure for  evaluating the performance of GENI’s backbone and access networks when carrying L2 VLANs;  start with the existing IP measurement tools including in the LAMP/perfSONAR tools, but consider tools that are specialized for evaluating the performance of L2 networks.  [[BR]]
    130 
    131 Define 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]]
     137*Assuming 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]]
     138
     139*Define a procedure for  evaluating the performance of GENI’s backbone and access networks when carrying L2 VLANs;  start with the existing IP measurement tools including in the LAMP/perfSONAR tools, but consider tools that are specialized for evaluating the performance of L2 networks.  [[BR]]
     140
     141*Define 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]]
    132142
    133143
     
    141151**Participate in defining the schema for the “measurement data object descriptor”, and uses of “descriptors” in tracking provenance. [[BR]]
    142152
    143 Work 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]]
    144 
    145 Modify 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]]
    146 
    147 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]]
    148 
    149 Add modules to your tools to create, gather and forward “resource event records”, that when logged could fully describe the sequence of an experiment. [[BR]]
     153*Work 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]]
     154
     155*Modify 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]]
     156
     157*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]]
     158
     159*Add modules to your tools to create, gather and forward “resource event records”, that when logged could fully describe the sequence of an experiment. [[BR]]
    150160 
    151 Work towards fitting your provenance tools into the  “experimenter’s portal”.  [[BR]]
     161*Work towards fitting your provenance tools into the  “experimenter’s portal”.  [[BR]]
    152162
    153163
     
    160170**Prototype and operate a GENI XML messaging service, with pub/sub, based on an XMPP server and XCP-0060.  [[BR]]
    161171
    162 Prototype 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]]
    163 
    164 Prototype and demonstrate using your pub/sub capability to transport and distribute standardized GENI “resource event records”, as defined by the NetKarma project.  [[BR]]
     172*Prototype 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]]
     173
     174*Prototype and demonstrate using your pub/sub capability to transport and distribute standardized GENI “resource event records”, as defined by the NetKarma project.  [[BR]]
    165175
    166176
     
    175185**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]]
    176186
    177 Enforce metadata schema on archived objects, and enable access control rights as defined by the MDA specification.  [[BR]]
    178 
    179 Evangelize and demonstrate how the MDA/DOR service can be used to archive published data.  [[BR]]
     187*Enforce metadata schema on archived objects, and enable access control rights as defined by the MDA specification.  [[BR]]
     188
     189*Evangelize and demonstrate how the MDA/DOR service can be used to archive published data.  [[BR]]
    180190
    181191