Changes between Version 25 and Version 26 of GEC14Agenda/IMDesignTopics


Ignore:
Timestamp:
06/26/12 15:24:06 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC14Agenda/IMDesignTopics

    v25 v26  
    6363
    6464
    65 Mike Zink will review:  [[BR]]
    66 
    67 * Current architecture, design and status. [[BR]]
    68 * Plan for GEC-14 tutorial [[BR]]
    69 
    70 * Next steps, during Spiral 5 [[BR]]
     65Summary:  [[BR]]
     66
     67 * Current architecture, design and status. [[BR]]
     68 * Plan for GEC-14 tutorial [[BR]]
     69
     70 * Next steps, during Spiral 5 [[BR]]
    7171
    7272
     
    8383[wiki:GEMINI  GEMINI wiki]  [[BR]]
    8484
    85 Goals:  [[BR]]
    86 
    87 * Includes LAMP code and features into GEMINI tools, to provides flexible tools based on perfSONAR for active infrastructure measurements [[BR]]
    88 * Includes INSTOOLS code and features into GEMINI tools, to gather basic host measurements [[BR]]
    89 * Later, integrate LAMP and INSTOOLS code and features into new code base for GEMINI tools.
    90 
    91 * First focus:  I&M use cases for infrastructure measurement
    92 * Include sharing of data with other users (e.g., operators), at an interface with authorization using a GENI credential  [[BR]]
    93 * Show how to monitor clusters/racks [[BR]]
    94 * Show how to measure Layer 2 and OpenFlow paths (with input from OnTimeMeasure project)
    95 
    96 * Second focus: I&M use cases for experiments [[BR]]
    97 * Gather basic host measurements (as was done by INSTOOLS using SNMP) [[BR]]
    98 * Show how to gather customized data from applications (as provided by OML Client)  [[BR]]
    99 
    100 * Spiral 4 supported aggregates:  protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]]
    101 * Spiral 5 supported aggregates:  ORCA servers/VMs and ExoGENI (RENCI) racks  [[BR]]
    102 
    103 * Continues INSTOOLS portal service, to find GUIs    [[BR]]
    104 * Continues LAMP local and global Unified Network Information Service (UNIS), to register available measurement data, and network topology  [[BR]]
    105 
    106 Martin Swany and Jim Griffioen will review:  [[BR]]
    107 
    108 * Current architecture, design and status. [[BR]]
    109 * Plan for GEC-14 tutorial [[BR]]
    110 
    111 * Next steps, during Spiral 5 [[BR]]
     85Goals  [[BR]]
     86
     87 * Includes LAMP code and features in GEMINI tools, to provides flexible tools based on perfSONAR for active infrastructure measurements [[BR]]
     88 * Includes INSTOOLS code and features in GEMINI tools, to gather basic host measurements [[BR]]
     89 * Later, integrates LAMP and INSTOOLS code and features into new code base for GEMINI tools. [[BR]]
     90
     91 * First focus:  I&M use cases for infrastructure measurement [[BR]]
     92 * Include sharing of data with other users (e.g., operators), at an interface with authorization using a GENI credential  [[BR]]
     93 * Show how to monitor clusters/racks [[BR]]
     94 * Show how to measure Layer 2 and OpenFlow paths (with input from OnTimeMeasure project) [[BR]]
     95
     96 * Second focus: I&M use cases for experiments [[BR]]
     97 * Gather basic host measurements (as was done by INSTOOLS using SNMP) [[BR]]
     98 * Show how to gather customized data from applications (as provided by OML Client)  [[BR]]
     99
     100 * Spiral 4 supported aggregates:  protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]]
     101 * Spiral 5 supported aggregates:  ORCA servers/VMs and ExoGENI (RENCI) racks  [[BR]]
     102
     103 * Continues INSTOOLS portal service, to find GUIs    [[BR]]
     104 * Continues LAMP local and global Unified Network Information Service (UNIS), to register available measurement data, and network topology  [[BR]]
     105
     106Summary  [[BR]]
     107
     108 * Current architecture, design and status. [[BR]]
     109 * Plan for GEC-14 tutorial [[BR]]
     110
     111 * Next steps, during Spiral 5 [[BR]]
    112112
    113113== 5)  Reports on I&M design topics ==
     
    120120
    121121Goals  [[BR]]
    122  Provide a concise definition of the environment where the GENI I&M tools will be tested.  [[BR]]
     122 * Provide a concise definition of the environment where the GENI I&M tools will be tested.  [[BR]]
    123123
    124124Tasks  [[BR]]
    125  Include:  [[BR]]
    126  User tools for experiment and measurement setup and orchestration [[BR]]
    127  Interfaces/protocols between user tools and GENI aggregates  [[BR]]
    128  Supported GENI aggregates  [[BR]]
     125 * Include:  [[BR]]
     126 * User tools for experiment and measurement setup and orchestration [[BR]]
     127 * Interfaces/protocols between user tools and GENI aggregates  [[BR]]
     128 * Supported GENI aggregates  [[BR]]
    129129
    130130Summary  [[BR]]
    131  [http://groups.geni.net/geni/wiki/InstMeasTopic_4.4GENIEnvironment  work in progress]  [[BR]]
    132  Current configuration (Spiral 4)  [[BR]]
    133  Next configuration (Spiral 5)  [[BR]]
     131 * [http://groups.geni.net/geni/wiki/InstMeasTopic_4.4GENIEnvironment  work in progress]  [[BR]]
     132 * Current configuration (Spiral 4)  [[BR]]
     133 * Next configuration (Spiral 5)  [[BR]]
    134134
    135135=== T8) GENI User Tools and Services ===
     
    139139
    140140Goals [[BR]]
    141  Work towards Max Ott's vision for experiment support  [[BR]]
    142  Provide a way for a GENI user (e.g., experimenter or operator) to access a wide variety of "GENI User Services", where each user service provides an interface (e.g., API or GUI) to the user.  Those user services with a GUI (web) interface are often called "portal services".[[BR]]
    143  Together, the "GENI User Services" should provide all of the functions the user needs to setup and run their experiment, then gather, analyze and present their measurement data.   [[BR]]
    144  These services should work together via APIs, etc., to streamline the experiment process. [[BR]]
     141 * Work towards Max Ott's vision for experiment support  [[BR]]
     142 * Provide a way for a GENI user (e.g., experimenter or operator) to access a wide variety of "GENI User Services", where each user service provides an interface (e.g., API or GUI) to the user.  Those user services with a GUI (web) interface are often called "portal services".[[BR]]
     143 * Together, the "GENI User Services" should provide all of the functions the user needs to setup and run their experiment, then gather, analyze and present their measurement data.   [[BR]]
     144 * These services should work together via APIs, etc., to streamline the experiment process. [[BR]]
    145145
    146146Tasks [[BR]]
    147  Based upon the configuration defined below, the implementation is split into: [[BR]]
     147 * Based upon the configuration defined below, the implementation is split into: [[BR]]
    148148 1)  A GENI User Workspace, which is a persistent Linux OS environment dedicated to the user, that serves as a container for multiple user tools [[BR]]
    149149 2)  Multiple GENI User Tools, where each provides a service with an interface or a "portal" to the user. [[BR]]
    150  Define, prototype, deploy and operate a GENI User Workspace. It can be hosted on a server dedicated to the user (even the user's laptop), or on a server hosting multiple user workspaces for multiple users.[[BR]]
    151  Gather the various "user tools" that have been implemented to date, and fit them into GENI User Workspace Service so that GENI I&M users can begin to conveniently conduct experiments or instrument infrastructure. [[BR]]
    152  Optimize "user tools" and their interfaces to better meet the needs of GENI users (e.g., experimenters and operators).  [[BR]]
    153  Use the "GENI User Workspace" to test the GIMI and GEMINI tools, and during their tutorials.
     150 * Define, prototype, deploy and operate a GENI User Workspace. It can be hosted on a server dedicated to the user (even the user's laptop), or on a server hosting multiple user workspaces for multiple users.[[BR]]
     151 * Gather the various "user tools" that have been implemented to date, and fit them into GENI User Workspace Service so that GENI I&M users can begin to conveniently conduct experiments or instrument infrastructure. [[BR]]
     152 * Optimize "user tools" and their interfaces to better meet the needs of GENI users (e.g., experimenters and operators).  [[BR]]
     153 * Use the "GENI User Workspace" to test the GIMI and GEMINI tools, and during their tutorials.
    154154
    155155Summary  [[BR]]
    156  [http://groups.geni.net/geni/wiki/InstMeasTopic_4.8PortalService  work in progress]  [[BR]]
    157  Current configuration (Spiral 4)  [[BR]]
    158  Next configuration (Spiral 5)  [[BR]]
     156 * [http://groups.geni.net/geni/wiki/InstMeasTopic_4.8PortalService  work in progress]  [[BR]]
     157 * Current configuration (Spiral 4)  [[BR]]
     158 * Next configuration (Spiral 5)  [[BR]]
    159159
    160160=== T5)  Descriptors, Objects and Registries  ===
     
    164164
    165165Tasks  [[BR]]
    166  Need to finalize MDOD schema, for XML file.  [http://groups.geni.net/geni/wiki/GEC11InstMeasWorkingSession#a2MeasurementDataObjectDescriptorMDOD  References]  [[BR]]
    167  Want to extend MDOD to cover all types of objects, i.e., software images.  (NetKarma)[[BR]]
    168  Want to use MDOD schema to define Event Record schema.  (NetKarma)[[BR]]
    169  Do we need MDOD registry?  Use UNIS lookup service? Include in iRODS? [[BR]]
    170  Need MDOD creation and editing service. (who?) [[BR]]
    171  Need Measurement Data Object identifiers (names);  sometimes need a persistent, public reference;  consider DataCite approach, which uses handle  [[BR]]
     166 * Need to finalize MDOD schema, for XML file.   [http://groups.geni.net/geni/wiki/GEC11InstMeasWorkingSession#a2MeasurementDataObjectDescriptorMDOD  References]  [[BR]]
     167 * Want to extend MDOD to cover all types of objects, i.e., software images.  (NetKarma)[[BR]]
     168 * Want to use MDOD schema to define Event Record schema.  (NetKarma)[[BR]]
     169 * Do we need MDOD registry?  Use UNIS lookup service? Include in iRODS? [[BR]]
     170 * Need MDOD creation and editing service. (who?) [[BR]]
     171 * Need Measurement Data Object identifiers (names);  sometimes need a persistent, public reference;  consider DataCite approach, which uses handle  [[BR]]
    172172
    173173Summary  [[BR]]
    174  [http://groups.geni.net/geni/wiki/InstMeasTopic_4.5DescriptorsObjectsRegistriesLookupService  work in progress]  [[BR]]
    175  v0.1 design reviewed at GEC13    [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T5%29%20%20MDOD%20Status%20-%20CNRI.pptx  slides] (Giridhar Manepalli)  Conclusion:  too complex  [[BR]]
    176  DRAFT simplified v0.2 design [  slides] (Harry Mussman)[[BR]]
    177 
    178 Discussion
    179  Who will review?  Shall we have a breakout meeting on Wed, 7/11? [[BR]]
    180  Who will implement? [[BR]]
    181  How will this be included into iRODS? [[BR]]
     174 * [http://groups.geni.net/geni/wiki/InstMeasTopic_4.5DescriptorsObjectsRegistriesLookupService  work in progress]  [[BR]]
     175 * v0.1 design reviewed at GEC13    [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T5%29%20%20MDOD%20Status%20-%20CNRI.pptx  slides] (Giridhar Manepalli)  Conclusion:  too complex  [[BR]]
     176 * DRAFT simplified v0.2 design [  slides] (Harry Mussman)[[BR]]
     177
     178Discussion
     179 * Who will review?  Shall we have a breakout meeting on Wed, 7/11? [[BR]]
     180 * Who will implement? [[BR]]
     181 * How will this be included into iRODS? [[BR]]
    182182 
    183183