Context Navigation

Changes between Version 18 and Version 19 of GEC13Agenda/InstrumentationAndMeasurement

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

Legend:

: Unmodified
: Added
: Removed
: Modified

GEC13Agenda/InstrumentationAndMeasurement

-                      v18
+                      v19
+== T4)  GENI Environment  ==
+Platform Targets  [[BR]]
+Experiment and Measurement Orchestration Tools  [[BR]]
+Interfaces/Protocols Between Tools and Services  [[BR]]
+=== T4)  GENI Environment  ===
+:35am  [[BR]]
+Team [[BR]]
+ Martin Swany (IU) [[BR]]
+ Jim Griffioen (U Kentucky) [[BR]]
+ Ilia Baldine, for ExoGENI racks (RENCI) [[BR]]
+ ?, for InstaGENI racks (?) [[BR]]
+ David Irwin (UMass Amherst) [[BR]]
+ Mike Zink (UMass Amherst) [[BR]]
+ Christoph Dwertmann (NICTA) [[BR]]
+ LEAD  Harry Mussman  (GPO) [[BR]]
+ Tom Mitchell (GPO) [[BR]]
+ Aaron Helsinger (GPO) [[BR]]
+ Marshall Brinn (GPO) [[BR]]
+ Vic Thomas (GPO)  [[BR]] [[BR]]
+Tasks  [[BR]]
+ Provide a concise definition of the environment where the GENI I&M tools will be tested, including:  [[BR]]
+ User tools for experiment and measurement setup and orchestration [[BR]]
+ Interfaces/protocols between user tools and GENI aggregates  [[BR]]
+ Supported GENI aggregtaes  [[BR]]
 [wiki:InstMeasTopic_4.4GENIEnvironment  Work in Progress]  [[BR]]
+)  Definition of topic:  [[BR]]
+a)  Platform targets: [[BR]]
+)  protoGENI servers/VMs [[BR]]
+)  ORCA servers/VMs [[BR]]
+)  WiMAX sites [[BR]]
+)  ExoGENI (RENCI) racks;  like ORCA [[BR]]
+)  TransCloud (HP) racks;  like protoGENI? [[BR]]
+)  PlanetLab
+b) Experiment and Measurement Orchestration tools: [[BR]]
+)  FLACK [[BR]]
+)  GUSH (with Omni) [[BR]]
+)  SFACE + RAVEN [[BR]]
+c) Interfaces/protocols between tools and services: [[BR]]
+)  protoGENI API, with protoGENI RSpec v2, for resource assignment [[BR]]
+)  GENI AM API, with protoGENI RSpec v2, for resource assignment [[BR]]
+)  ns for topology [[BR]]
+)  ssh for image loading [[BR]]
+)  OMF messages for orchestration [[BR]]
+)  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]]
+== T5)  Descriptors, Objects and Registries  ==
+Descriptor Schema and Registry Service  [[BR]]
+Object Names and Registry Service  [[BR]]
+Summary of current status [[BR]]
+=== T5)  Descriptors, Objects and Registries  ===
+:50am [[BR]]
+Team  [[BR]]
+ Jason Zurawski (Internet2) [[BR]]
+ Ezra Kissel (U Delaware) [[BR]]
+ Eric Boyd (Internet2) [[BR]]
+ Beth Plale (IU) [[BR]]
+ Chris Small (GEMINI, IU) [[BR]]
+ Scott Jensen (Indiana U) [[BR]]
+ Larry Lannom (CNRI) [[BR]]
+ LEAD Giridhar Manepalli (CNRI) [[BR]]
+ Deniz Gurken (GIMI, UH) [[BR]]
+ Harry Mussman (GPO)  [[BR]] [[BR]]
+Tasks  [[BR]]
+ Need to finalize MDOD schema, for XML file.  [http://groups.geni.net/geni/wiki/GEC11InstMeasWorkingSession#a2MeasurementDataObjectDescriptorMDOD  References]  [[BR]]
+ Want to extend MDOD to cover all types of objects, i.e., software images.  (NetKarma)[[BR]]
+ Want to use MDOD schema to define Event Record schema.  (NetKarma)[[BR]]
+ Do we need MDOD registry?  Use UNIS lookup service?  Use DOR registry? Include in iRODS? Consider IF-MAP server? [[BR]]
+ Need MDOD creation and editing service. (CNRI) [[BR]]
+ Need Measurement Data Object identifiers (names);  sometimes need a persistent, public reference;  consider DataCite approach, which uses handle  [[BR]]
 [wiki:InstMeasTopic_4.5DescriptorsObjectsRegistriesLookupService  Work in Progress]  [[BR]]
+) Goals  [[BR]]
+) Tasks  [[BR]]
+a)  Need to finalize MDOD schema, for XML file.  [http://groups.geni.net/geni/wiki/GEC11InstMeasWorkingSession#a2MeasurementDataObjectDescriptorMDOD  References]  [[BR]]
+b)  Want to extend MDOD to cover all types of objects, i.e., software images.  (NetKarma)[[BR]]
+c)  Want to use MDOD schema to define Event Record schema.  (NetKarma)[[BR]]
+d)  Do we need MDOD registry?  Use UNIS lookup service?  Use DOR registry? Include in iRODS? Consider IF-MAP server? [[BR]]
+e)  Need MDOD creation and editing service. (CNRI) [[BR]]
+f)  Need Measurement Data Object identifiers (names);  sometimes need a persistent, public reference;  consider DataCite approach, which uses handle  [[BR]]
+) Team  [[BR]]
+Jason Zurawski (Internet2) [[BR]]
+Ezra Kissel (U Delaware) [[BR]]
+Eric Boyd (Internet2) [[BR]]
+Beth Plale (IU) [[BR]]
+Chris Small (GEMINI, IU) [[BR]]
+Scott Jensen (Indiana U) [[BR]]
+Larry Lannom (CNRI) [[BR]]
+LEAD Giridhar Manepalli (CNRI) [[BR]]
+Deniz Gurken (GIMI, UH) [[BR]]
+Harry Mussman (GPO)  [[BR]] [[BR]]
+== T6)  XML Messaging Service ==
+XML Messaging Service  [[BR]]
+[wiki:InstMeasTopic_4.6MessagingService  Work in Progress]  [[BR]]
+)  Goals   [[BR]]
+ 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]]
+ The OMF messages are carried between an EC and RC by an XML pub/sub messaging service, based on an XMPP server.  [[BR]]
+ For GENI, an XML Messaging service will be provided to carry these OMF messages, and thus enable orchestration.  [[BR]]
+ However, such a service may have other useful functions, such as transporting Event Records (ERs).  [[BR]]
+ To be generally useful, authentication and authorization functions must be provided.   [[BR]]
+ For a detailed list of all goals defined for the XML Messaging service, see the Spiral 4 SOW of the IMF project.  [[BR]]
+)  Tasks   [[BR]]
+ Define, prototype, demonstrate and operate a GENI Messaging service, starting at GEC13. [[BR]]
+ 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]]
+ Support use in GENI by many tools, including  GEMINI and GIMI I&M tools  [[BR]]
+ Define operations plan for XML Messaging service.  [[BR]]
+)  Team   [[BR]]
+Summary of current status [[BR]]
+=== T6)  XML Messaging Service ===
+:05am  [[BR]]
+Team   [[BR]]
  Rudra Dutta (NCSU) [[BR]]
  LEAD Anirban Mandal (RENCI) [[BR]]
 …
  Harry Mussman (GPO) [[BR]]
+== T7)  Measurement Information (MI) Service ==
+Lookup Service  [[BR]]
+[wiki:InstMeasTopic_4.7LookupService  Work in Progress]  [[BR]]
+)  Goals  [[BR]]
+ 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.
+ In addition, a similar Topology Service is used to store the topology of the network being examined.
+ Together, these services are combined in the Unified Network Information Service (UNIS).
+ 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]]
+ For GENI, the Measurement Information service (MI) will be provided to serve the need for a global UNIS service.
+ Can the MI service be used for other registry functions?
+ Can the MI service be used for finding web interfaces, and other types of portals?
+ Can the MI service be used to provide topology information to assist resource assignment and stitching in GENI?
+)  Tasks   [[BR]]
+Tasks   [[BR]]
+ Define, prototype, demonstrate and operate a GENI Messaging service, starting at GEC13. [[BR]]
+ 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]]
+ Support use in GENI by many tools, including  GEMINI and GIMI I&M tools  [[BR]]
+ Define operations plan for XML Messaging service.  [[BR]]
+[wiki:InstMeasTopic_4.6MessagingService  Work in Progress]  [[BR]]
+Summary of current status [[BR]]
+=== T7)  Measurement Information (MI) Service ===
+:15am  [[BR]]
+Team  [[BR]]
+ LEAD  ? (GEMINI)  [[BR]]
+ Giridhar Manepalli (CNRI)  [[BR]]
+ Harry Mussman (GPO)  [[BR]]
+Tasks   [[BR]]
  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]]
 ) Refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances: [[BR]]
 ) Update topology model to Rspec version 3 and AM API (February 2012) [[BR]]
 …
 ) Complete noSQL (MongoDB) backend (September 2012)  [[BR]]
 ) Unify Perl and Python implementations (September 2012) [[BR]]
  Define, prototype, demonstrate and operate a MI service, starting in May, 2012. [[BR]]
  Support use in GENI by many tools, including  GEMINI and GIMI I&M tools  [[BR]]
  Define operations plan for MI service.  [[BR]]
+)  Team  [[BR]]
+ ? (GEMINI)  [[BR]]
+ Giridhar Manepalli (CNRI)  [[BR]]
+ Harry Mussman (GPO)  [[BR]]
+== T8) GENI User Services ==
+Portal Service  [[BR]]
+[wiki:InstMeasTopic_4.7LookupService  Work in Progress]  [[BR]]
+Summary of current status [[BR]]
+=== T8) GENI User Services ===
+:25am  [[BR]]
+Team [[BR]]
+ Jim Griffioen and/or Charles Carpenter (INSTOOLS and GEMINI, U Kentucky)  [[BR]]
+ Max Ott and/or Christoph Dwertmann (NICTA)  [[BR]]
+ Chris Small  (NetKarma,  IU)  [[BR]]
+ Ahmed El-Hassany (IU) [[BR]]
+ LEAD Jeanne Ohren (GPO)[[BR]]
+ Harry Mussman  (GPO) [[BR]]
+Goals [[BR]]
+ Work towards Max Ott's vision for experiment support  [[BR]]
+ 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]]
+ 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]]
+ These services should work together via APIs, etc., to streamline the experiment process. [[BR]]
+Tasks [[BR]]
+ Based upon the configuration defined below, the implementation is split into: [[BR]]
+)  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]]
+)  Multiple GENI User Tools, where each provides a service with an interface or a "portal" to the user. [[BR]]
+ Define, prototype, deploy and operate a GENI User Workspace Service. [[BR]]
+ 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]]
+ Optimize "user tools" and their interfaces to better meet the needs of GENI users (e.g., experimenters and operators).  [[BR]]
 [wiki:InstMeasTopic_4.8PortalService  Work in Progress]  [[BR]]
+)  Goals [[BR]]
+ Work towards Max Ott's vision for experiment support  [[BR]]
+ 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]]
+ 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]]
+ These services should work together via APIs, etc., to streamline the experiment process. [[BR]]
+)  Tasks [[BR]]
+ Based upon the configuration defined below, the implementation is split into: [[BR]]
+)  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]]
+)  Multiple GENI User Tools, where each provides a service with an interface or a "portal" to the user. [[BR]]
+ Define, prototype, deploy and operate a GENI User Workspace Service. [[BR]]
+ 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]]
+ Optimize "user tools" and their interfaces to better meet the needs of GENI users (e.g., experimenters and operators).  [[BR]]
+)  Team [[BR]]
+  Jim Griffioen and/or Charles Carpenter (INSTOOLS and GEMINI, U Kentucky)  [[BR]]
+  Max Ott and/or Christoph Dwertmann (NICTA)  [[BR]]
+  Chris Small  (NetKarma,  IU)  [[BR]]
+  Ahmed El-Hassany (IU) [[BR]]
+  Jeanne Ohren (GPO)[[BR]]
+  Harry Mussman  (GPO) [[BR]]
+== T9)  Digital Object Archive (DOA) Service ==
+User Workspace and Archive Services  [[BR]]
+Summary of current status [[BR]]
+=== T9)  Digital Object Archive (DOA) Service ===
+:40am [[BR]]
+Team [[BR]]
+ Co-LEAD Giridhar Manepalli (CNRI) [[BR]]
+ Co-LEAD  Shu Huang (RENCI) [[BR]]
+ Larry Lannom (CNRI) [[BR]]
+ Wesley Wu (U Kentucky) [[BR]]
+ Hussam Nasir (U Kentucky) [[BR]]
+ Chris Small  (NetKarma, IU) [[BR]]
+ Jeannie Ohren (GPO) [[BR]]
+Tasks
+ Start with CNRI prototype digital object archive service [[BR]]
+ Plan transition to use of iRODS service [[BR]]
+ How to move data to service:  move file;  move SQL DB;  or? [[BR]]
+ How is persistent object identifier (i.e., handle) generated?  also registered?  and later resolved?
+ How are partitions for different users managed? [[BR]]
+ How is data in MDOD used to set archive sharing policy?  what is required in MDOD? [[BR]]
+ Operations plan for Digital Object Archive Service. [[BR]]
 [wiki:InstMeasTopic_4.9ArchiveService  Work in Progress]  [[BR]]
+)  Definition of topic:  [[BR]]
+ a)  Consider CNRI prototype user workspace and archive service [[BR]]
+ b)  Consider U Kentucky archive service [[BR]]
+ c)  Use iRODS service? [[BR]]
+ d)  How to move data to service:  move file;  move SQL DB;  or? [[BR]]
+ e)  How are partitions for different users managed? [[BR]]
+ f)  How is data in MDOD used to set archive sharing policy?  what is required in MDOD? [[BR]]
+ g)  Operations plan for Archive Service. [[BR]]
+)  Who: Giridhar Manepalli (CNRI);  LEAD  Shu Huang (RENCI) ;  Larry Lannom (CNRI);  Wesley Wu (U Kentucky);  Hussam Nasir (U Kentucky);  Chris Small  (NetKarma, IU) [[BR]]
+== T10) List of Operational Services ==
+Persistent Operational Services  [[BR]]
+Services Shared by GIMI and GEMINI  [[BR]]
+Summary of current status [[BR]]
+=== T10) List of Operational Services ===
+(no report)  [[BR]]
+Team [[BR]]
+ Mike Zink (UMass Amherst) [[BR]]
+ Martin Swany (Inidana U) [[BR]]
+ Jim Griffioen (U Kentucky) [[BR]]
+ Giridhar Manepalli (CNRI) [[BR]]
+ Marshall Brinn (GPO) [[BR]]
+ Jeanne Ohren (GPO)  [[BR]]
+ Harry Mussman (GPO)   [[BR]]
+Tasks:
+ What persistent operational services must be supported: [[BR]]
+ a)  Descriptor registry   required?  use UNIS?  DOR?  iRODS? IF-MAP? [[BR]]
+ b)  Object registry   required?  use DOR? [[BR]]
+ c)  XML Messaging service [[BR]]
+ d)  Measurement Information (MI)service  [[BR]]
+ e)  GENI User services [[BR]]
+ f) Digital Object Archive (DOA) service [[BR]]
+ Can all services can be shared by GIMI and GEMINI tools? [[BR]]
+ How do these relate to other GENI services/functions, including clearinghouse?
 [wiki:InstMeasTopic_4.10OperationalServices  Work in Progress]  [[BR]]
+)  What persistent operational services must be supported: [[BR]]
+  a)  Descriptor registry   required?  use UNIS?  DOR?  iRODS? IF-MAP? [[BR]]
+  b)  Object registry   required?  use DOR? [[BR]]
+  c)  XML Messaging service [[BR]]
+  d)  Measurement Information (MI)service  [[BR]]
+  e)  GENI User services [[BR]]
+  f) Digital Object Archive (DOA) service [[BR]]
+)  Can all services can be shared by GIMI and GEMINI tools? [[BR]]
+)  How do these relate to other GENI services/functions, including clearinghouse?
+)  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]]
+=== Discussion of next steps ===
+:55am [[BR]]
 == 3)  Adjourn ==