Changes between Version 18 and Version 19 of GEC13Agenda/InstrumentationAndMeasurement


Ignore:
Timestamp:
03/02/12 11:36:58 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC13Agenda/InstrumentationAndMeasurement

    v18 v19  
    101101
    102102
    103 == T4)  GENI Environment  ==
    104 Platform Targets  [[BR]]
    105 Experiment and Measurement Orchestration Tools  [[BR]]
    106 Interfaces/Protocols Between Tools and Services  [[BR]]
     103=== T4)  GENI Environment  ===
     10410:35am  [[BR]]
     105
     106Team [[BR]]
     107 Martin Swany (IU) [[BR]]
     108 Jim Griffioen (U Kentucky) [[BR]]
     109 Ilia Baldine, for ExoGENI racks (RENCI) [[BR]]
     110 ?, for InstaGENI racks (?) [[BR]]
     111 David Irwin (UMass Amherst) [[BR]]
     112 Mike Zink (UMass Amherst) [[BR]]
     113 Christoph Dwertmann (NICTA) [[BR]]
     114 LEAD  Harry Mussman  (GPO) [[BR]]
     115 Tom Mitchell (GPO) [[BR]]
     116 Aaron Helsinger (GPO) [[BR]]
     117 Marshall Brinn (GPO) [[BR]]
     118 Vic Thomas (GPO)  [[BR]] [[BR]]
     119
     120Tasks  [[BR]]
     121 Provide a concise definition of the environment where the GENI I&M tools will be tested, including:  [[BR]]
     122 User tools for experiment and measurement setup and orchestration [[BR]]
     123 Interfaces/protocols between user tools and GENI aggregates  [[BR]]
     124 Supported GENI aggregtaes  [[BR]]
    107125
    108126[wiki:InstMeasTopic_4.4GENIEnvironment  Work in Progress]  [[BR]]
    109127
    110 1)  Definition of topic:  [[BR]]
    111 
    112 a)  Platform targets: [[BR]]
    113   1)  protoGENI servers/VMs [[BR]]
    114   2)  ORCA servers/VMs [[BR]]
    115   3)  WiMAX sites [[BR]]
    116   4)  ExoGENI (RENCI) racks;  like ORCA [[BR]]
    117   5)  TransCloud (HP) racks;  like protoGENI? [[BR]]
    118   6)  PlanetLab
    119 
    120 b) Experiment and Measurement Orchestration tools: [[BR]]
    121   1)  FLACK [[BR]]
    122   2)  GUSH (with Omni) [[BR]]
    123   3)  SFACE + RAVEN [[BR]]
    124 
    125 c) Interfaces/protocols between tools and services: [[BR]]
    126   1)  protoGENI API, with protoGENI RSpec v2, for resource assignment [[BR]]
    127   2)  GENI AM API, with protoGENI RSpec v2, for resource assignment [[BR]]
    128   3)  ns for topology [[BR]]
    129   4)  ssh for image loading [[BR]]
    130   5)  OMF messages for orchestration [[BR]]
    131 
    132 2)  Who: Martin Swany (IU);  Jim Griffioen (U Kentucky);  Ilia Baldine, for ExoGENI racks (RENCI);  ?, for InstaGENI racks (?);  David Irwin (UMass Amherst);  Mike Zink (UMass Amherst);  Christoph Dwertmann (NICTA);  LEAD  Harry Mussman  (GPO);  Tom Mitchell (GPO);  Aaron Helsinger (GPO);  Marshall Brinn (GPO);  Vic Thomas (GPO)  [[BR]]
    133 
    134 
    135 
    136 == T5)  Descriptors, Objects and Registries  ==
    137 Descriptor Schema and Registry Service  [[BR]]
    138 Object Names and Registry Service  [[BR]]
     128Summary of current status [[BR]]
     129
     130
     131
     132
     133
     134=== T5)  Descriptors, Objects and Registries  ===
     13510:50am [[BR]]
     136
     137Team  [[BR]]
     138 Jason Zurawski (Internet2) [[BR]]
     139 Ezra Kissel (U Delaware) [[BR]]
     140 Eric Boyd (Internet2) [[BR]]
     141 Beth Plale (IU) [[BR]]
     142 Chris Small (GEMINI, IU) [[BR]]
     143 Scott Jensen (Indiana U) [[BR]]
     144 Larry Lannom (CNRI) [[BR]]
     145 LEAD Giridhar Manepalli (CNRI) [[BR]]
     146 Deniz Gurken (GIMI, UH) [[BR]]
     147 Harry Mussman (GPO)  [[BR]] [[BR]]
     148
     149Tasks  [[BR]]
     150 Need to finalize MDOD schema, for XML file.  [http://groups.geni.net/geni/wiki/GEC11InstMeasWorkingSession#a2MeasurementDataObjectDescriptorMDOD  References]  [[BR]]
     151 Want to extend MDOD to cover all types of objects, i.e., software images.  (NetKarma)[[BR]]
     152 Want to use MDOD schema to define Event Record schema.  (NetKarma)[[BR]]
     153 Do we need MDOD registry?  Use UNIS lookup service?  Use DOR registry? Include in iRODS? Consider IF-MAP server? [[BR]]
     154 Need MDOD creation and editing service. (CNRI) [[BR]]
     155 Need Measurement Data Object identifiers (names);  sometimes need a persistent, public reference;  consider DataCite approach, which uses handle  [[BR]]
    139156
    140157[wiki:InstMeasTopic_4.5DescriptorsObjectsRegistriesLookupService  Work in Progress]  [[BR]]
    141158
    142159
    143 1) Goals  [[BR]]
    144 
    145 
    146 
    147 2) Tasks  [[BR]]
    148 
    149 a)  Need to finalize MDOD schema, for XML file.  [http://groups.geni.net/geni/wiki/GEC11InstMeasWorkingSession#a2MeasurementDataObjectDescriptorMDOD  References]  [[BR]]
    150 b)  Want to extend MDOD to cover all types of objects, i.e., software images.  (NetKarma)[[BR]]
    151 c)  Want to use MDOD schema to define Event Record schema.  (NetKarma)[[BR]]
    152 d)  Do we need MDOD registry?  Use UNIS lookup service?  Use DOR registry? Include in iRODS? Consider IF-MAP server? [[BR]]
    153 e)  Need MDOD creation and editing service. (CNRI) [[BR]]
    154 f)  Need Measurement Data Object identifiers (names);  sometimes need a persistent, public reference;  consider DataCite approach, which uses handle  [[BR]]
    155 
    156 
    157 
    158 3) Team  [[BR]]
    159 
    160 Jason Zurawski (Internet2) [[BR]]
    161 Ezra Kissel (U Delaware) [[BR]]
    162 Eric Boyd (Internet2) [[BR]]
    163 Beth Plale (IU) [[BR]]
    164 Chris Small (GEMINI, IU) [[BR]]
    165 Scott Jensen (Indiana U) [[BR]]
    166 Larry Lannom (CNRI) [[BR]]
    167 LEAD Giridhar Manepalli (CNRI) [[BR]]
    168 Deniz Gurken (GIMI, UH) [[BR]]
    169 Harry Mussman (GPO)  [[BR]] [[BR]]
    170 
    171 
    172 
    173 == T6)  XML Messaging Service ==
    174 XML Messaging Service  [[BR]]
    175 
    176 [wiki:InstMeasTopic_4.6MessagingService  Work in Progress]  [[BR]]
    177 
    178 
    179 
    180 1)  Goals   [[BR]]
    181 
    182  In I&M, a Measurement Orchestration (MO) service needs to interact with the I&M services;  one way to do so is to use the OMF interface, currently used (for example) by the OMF Experiment Controller to command an OMF Resource Controller (RC) that is installed next to an application.  [[BR]]
    183 
    184  The OMF messages are carried between an EC and RC by an XML pub/sub messaging service, based on an XMPP server.  [[BR]]
    185 
    186  For GENI, an XML Messaging service will be provided to carry these OMF messages, and thus enable orchestration.  [[BR]]
    187 
    188  However, such a service may have other useful functions, such as transporting Event Records (ERs).  [[BR]]
    189 
    190  To be generally useful, authentication and authorization functions must be provided.   [[BR]]
    191  
    192  For a detailed list of all goals defined for the XML Messaging service, see the Spiral 4 SOW of the IMF project.  [[BR]]
    193 
    194  
    195 2)  Tasks   [[BR]]
    196 
    197  Define, prototype, demonstrate and operate a GENI Messaging service, starting at GEC13. [[BR]]
    198 
    199  The XML Mesaaging service will be built by the IMF project.  For a detailed task list, see the Spiral 4 SOW of the IMF project. [[BR]]
    200 
    201  Support use in GENI by many tools, including  GEMINI and GIMI I&M tools  [[BR]]
    202 
    203  Define operations plan for XML Messaging service.  [[BR]]
    204 
    205 
    206 3)  Team   [[BR]]
    207  
     160Summary of current status [[BR]]
     161
     162
     163
     164=== T6)  XML Messaging Service ===
     16511:05am  [[BR]]
     166
     167Team   [[BR]]
    208168 Rudra Dutta (NCSU) [[BR]]
    209169 LEAD Anirban Mandal (RENCI) [[BR]]
     
    212172 Harry Mussman (GPO) [[BR]]
    213173
    214 
    215 == T7)  Measurement Information (MI) Service ==
    216 Lookup Service  [[BR]]
    217 
    218 [wiki:InstMeasTopic_4.7LookupService  Work in Progress]  [[BR]]
    219 
    220 1)  Goals  [[BR]]
    221 
    222  A Lookup Service is a type of registry defined in the perfSONAR toolset;  the availability of MD at perfSONAR interfaces MC services is registered there, using metadata describing the data and its location.
    223 
    224  In addition, a similar Topology Service is used to store the topology of the network being examined. 
    225 
    226  Together, these services are combined in the Unified Network Information Service (UNIS). 
    227 
    228  The GEMINI project includes perfSONAR tools, and requires UNIS functions.  Some will be provided locally (within the slice), but a global service is required if available MD is to be registered, so that users can find it and get it.  [[BR]]
    229 
    230  For GENI, the Measurement Information service (MI) will be provided to serve the need for a global UNIS service.
    231 
    232  Can the MI service be used for other registry functions?
    233 
    234  Can the MI service be used for finding web interfaces, and other types of portals?
    235 
    236  Can the MI service be used to provide topology information to assist resource assignment and stitching in GENI? 
    237 
    238 2)  Tasks   [[BR]]
    239 
     174 
     175Tasks   [[BR]]
     176 Define, prototype, demonstrate and operate a GENI Messaging service, starting at GEC13. [[BR]]
     177 The XML Mesaaging service will be built by the IMF project.  For a detailed task list, see the Spiral 4 SOW of the IMF project. [[BR]]
     178 Support use in GENI by many tools, including  GEMINI and GIMI I&M tools  [[BR]]
     179 Define operations plan for XML Messaging service.  [[BR]]
     180
     181[wiki:InstMeasTopic_4.6MessagingService  Work in Progress]  [[BR]]
     182
     183Summary of current status [[BR]]
     184
     185
     186=== T7)  Measurement Information (MI) Service ===
     18711:15am  [[BR]]
     188
     189Team  [[BR]]
     190 LEAD  ? (GEMINI)  [[BR]]
     191 Giridhar Manepalli (CNRI)  [[BR]]
     192 Harry Mussman (GPO)  [[BR]]
     193
     194Tasks   [[BR]]
    240195 The MI service will be built by the GEMINI project using UNIS technology;  see the Spiral 4 SOW of the GEMINI project for the detailed steps, which include:  [[BR]]
    241 
    242196 1) Refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances: [[BR]]
    243197 2) Update topology model to Rspec version 3 and AM API (February 2012) [[BR]]
     
    246200 5) Complete noSQL (MongoDB) backend (September 2012)  [[BR]]
    247201 6) Unify Perl and Python implementations (September 2012) [[BR]]
    248 
    249202 Define, prototype, demonstrate and operate a MI service, starting in May, 2012. [[BR]]
    250 
    251203 Support use in GENI by many tools, including  GEMINI and GIMI I&M tools  [[BR]]
    252 
    253204 Define operations plan for MI service.  [[BR]]
    254205
    255 
    256 3)  Team  [[BR]]
    257  
    258  ? (GEMINI)  [[BR]]
    259  Giridhar Manepalli (CNRI)  [[BR]]
    260  Harry Mussman (GPO)  [[BR]]
    261 
    262 
    263 
    264 
    265 == T8) GENI User Services ==
    266 Portal Service  [[BR]]
     206[wiki:InstMeasTopic_4.7LookupService  Work in Progress]  [[BR]]
     207
     208Summary of current status [[BR]]
     209
     210
     211=== T8) GENI User Services ===
     21211:25am  [[BR]]
     213
     214Team [[BR]]
     215 Jim Griffioen and/or Charles Carpenter (INSTOOLS and GEMINI, U Kentucky)  [[BR]]
     216 Max Ott and/or Christoph Dwertmann (NICTA)  [[BR]]
     217 Chris Small  (NetKarma,  IU)  [[BR]]
     218 Ahmed El-Hassany (IU) [[BR]]
     219 LEAD Jeanne Ohren (GPO)[[BR]]
     220 Harry Mussman  (GPO) [[BR]]
     221
     222Goals [[BR]]
     223 Work towards Max Ott's vision for experiment support  [[BR]]
     224 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]]
     225 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 the measurement data.   [[BR]]
     226 These services should work together via APIs, etc., to streamline the experiment process. [[BR]]
     227
     228Tasks [[BR]]
     229 Based upon the configuration defined below, the implementation is split into: [[BR]]
     230 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]]
     231 2)  Multiple GENI User Tools, where each provides a service with an interface or a "portal" to the user. [[BR]]
     232
     233 Define, prototype, deploy and operate a GENI User Workspace Service. [[BR]]
     234 Gather the various "user tools" that have been implemented to date, and fit into GENI User Workspace Service so that GENI I&M users can begin to conveniently conduct experiments or instrument infrastructure. [[BR]]
     235 Optimize "user tools" and their interfaces to better meet the needs of GENI users (e.g., experimenters and operators).  [[BR]]
    267236
    268237[wiki:InstMeasTopic_4.8PortalService  Work in Progress]  [[BR]]
    269238
    270 1)  Goals [[BR]]
    271 
    272  Work towards Max Ott's vision for experiment support  [[BR]]
    273 
    274  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]]
    275 
    276  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 the measurement data.   [[BR]]
    277 
    278  These services should work together via APIs, etc., to streamline the experiment process. [[BR]]
    279 
    280 2)  Tasks [[BR]]
    281 
    282  Based upon the configuration defined below, the implementation is split into: [[BR]]
    283 
    284  1)  A GENI User Workspace Service, which is a persistent Linux OS environment dedicated to the user, that serves as a container for multiple user tools [[BR]]
    285 
    286  2)  Multiple GENI User Tools, where each provides a service with an interface or a "portal" to the user. [[BR]]
    287 
    288  Define, prototype, deploy and operate a GENI User Workspace Service. [[BR]]
    289 
    290  Gather the various "user tools" that have been implemented to date, and fit into GENI User Workspace Service so that GENI I&M users can begin to conveniently conduct experiments or instrument infrastructure. [[BR]]
    291 
    292  Optimize "user tools" and their interfaces to better meet the needs of GENI users (e.g., experimenters and operators).  [[BR]]
    293 
    294 3)  Team [[BR]]
    295  
    296   Jim Griffioen and/or Charles Carpenter (INSTOOLS and GEMINI, U Kentucky)  [[BR]]
    297   Max Ott and/or Christoph Dwertmann (NICTA)  [[BR]]
    298   Chris Small  (NetKarma,  IU)  [[BR]]
    299   Ahmed El-Hassany (IU) [[BR]]
    300   Jeanne Ohren (GPO)[[BR]]
    301   Harry Mussman  (GPO) [[BR]]
    302 
    303 
    304 
    305 
    306 
    307 == T9)  Digital Object Archive (DOA) Service ==
    308 User Workspace and Archive Services  [[BR]]
     239Summary of current status [[BR]]
     240
     241
     242
     243=== T9)  Digital Object Archive (DOA) Service ===
     24411:40am [[BR]]
     245
     246Team [[BR]]
     247 Co-LEAD Giridhar Manepalli (CNRI) [[BR]]
     248 Co-LEAD  Shu Huang (RENCI) [[BR]]
     249 Larry Lannom (CNRI) [[BR]]
     250 Wesley Wu (U Kentucky) [[BR]]
     251 Hussam Nasir (U Kentucky) [[BR]]
     252 Chris Small  (NetKarma, IU) [[BR]]
     253 Jeannie Ohren (GPO) [[BR]]
     254
     255Tasks
     256 Start with CNRI prototype digital object archive service [[BR]]
     257 Plan transition to use of iRODS service [[BR]]
     258 How to move data to service:  move file;  move SQL DB;  or? [[BR]]
     259 How is persistent object identifier (i.e., handle) generated?  also registered?  and later resolved?
     260 How are partitions for different users managed? [[BR]]
     261 How is data in MDOD used to set archive sharing policy?  what is required in MDOD? [[BR]]
     262 Operations plan for Digital Object Archive Service. [[BR]]
     263
    309264
    310265[wiki:InstMeasTopic_4.9ArchiveService  Work in Progress]  [[BR]]
    311266
    312 1)  Definition of topic:  [[BR]]
    313 
    314  a)  Consider CNRI prototype user workspace and archive service [[BR]]
    315  b)  Consider U Kentucky archive service [[BR]]
    316  c)  Use iRODS service? [[BR]]
    317  d)  How to move data to service:  move file;  move SQL DB;  or? [[BR]]
    318  e)  How are partitions for different users managed? [[BR]]
    319  f)  How is data in MDOD used to set archive sharing policy?  what is required in MDOD? [[BR]]
    320  g)  Operations plan for Archive Service. [[BR]]
    321 
    322 2)  Who: Giridhar Manepalli (CNRI);  LEAD  Shu Huang (RENCI) ;  Larry Lannom (CNRI);  Wesley Wu (U Kentucky);  Hussam Nasir (U Kentucky);  Chris Small  (NetKarma, IU) [[BR]]
    323 
    324 
    325 == T10) List of Operational Services ==
    326 Persistent Operational Services  [[BR]]
    327 Services Shared by GIMI and GEMINI  [[BR]]
     267
     268Summary of current status [[BR]]
     269
     270
     271
     272
     273
     274=== T10) List of Operational Services ===
     275(no report)  [[BR]]
     276
     277Team [[BR]]
     278 Mike Zink (UMass Amherst) [[BR]]
     279 Martin Swany (Inidana U) [[BR]]
     280 Jim Griffioen (U Kentucky) [[BR]]
     281 Giridhar Manepalli (CNRI) [[BR]]
     282 Marshall Brinn (GPO) [[BR]]
     283 Jeanne Ohren (GPO)  [[BR]]
     284 Harry Mussman (GPO)   [[BR]]
     285
     286Tasks:
     287 What persistent operational services must be supported: [[BR]]
     288 a)  Descriptor registry   required?  use UNIS?  DOR?  iRODS? IF-MAP? [[BR]]
     289 b)  Object registry   required?  use DOR? [[BR]]
     290 c)  XML Messaging service [[BR]]
     291 d)  Measurement Information (MI)service  [[BR]]
     292 e)  GENI User services [[BR]]
     293 f) Digital Object Archive (DOA) service [[BR]]
     294 Can all services can be shared by GIMI and GEMINI tools? [[BR]]
     295 How do these relate to other GENI services/functions, including clearinghouse?
     296
    328297
    329298[wiki:InstMeasTopic_4.10OperationalServices  Work in Progress]  [[BR]]
    330299
    331 1)  What persistent operational services must be supported: [[BR]]
    332 
    333   a)  Descriptor registry   required?  use UNIS?  DOR?  iRODS? IF-MAP? [[BR]]
    334   b)  Object registry   required?  use DOR? [[BR]]
    335   c)  XML Messaging service [[BR]]
    336   d)  Measurement Information (MI)service  [[BR]]
    337   e)  GENI User services [[BR]]
    338   f) Digital Object Archive (DOA) service [[BR]]
    339 
    340 2)  Can all services can be shared by GIMI and GEMINI tools? [[BR]]
    341 
    342 3)  How do these relate to other GENI services/functions, including clearinghouse?
    343 
    344 4)  Who: Mike Zink (UMass Amherst);  Martin Swany (Inidana U);  Jim Griffioen (U Kentucky);  Giridhar Manepalli (CNRI);  Aaron Helsinger (GPO);  Jeanne Ohren (GPO);  Harry Mussman (GPO)   [[BR]]
    345 
    346 
     300
     301=== Discussion of next steps ===
     30211:55am [[BR]]
    347303
    348304== 3)  Adjourn ==