Changes between Initial Version and Version 1 of InstMeasCurrentDesignTopicsAll

Timestamp:

01/19/12 18:00:39 (12 years ago)

Author:

hmussman@bbn.com

Comment:

--

InstMeasCurrentDesignTopicsAll

@@ +1 @@
+= 4)  GENI I&M Priority Design Topics  =
+
+
+== Description == 
+
+These are the GENI I&M priority design topics that must be resolved to allow the current GENI I&M projects to proceed, particularly the large Sol 3 project (GIMI and GEMINI)  [[BR]]
+
+These topics were identified and reviewed at the GEC12 I&M meeting.  [[BR]]
+
+
+== Goals ==
+
+Resolve between now (GEC12) and GEC13.  [[BR]]
+
+Simplify where possible!   [[BR]]
+
+== Approach ==
+
+Form teams for each topic, and identify a LEAD for each topic. [[BR]
+
+Teams should meet by confernce call, or in person, and complete a report for presentation at GEC13.  [[BR]]
+
+
+== 4.1) List of All Identified Topics ==
+ 
+List:  [[BR]]
+
+a)  I&M Use Cases for Experiments  [[BR]]
+
+b)  I&M Use Cases for Infrastructure Measurement  [[BR]]
+
+c)  Platform Targets  [[BR]]
+
+d)  Experiment and Measurement Orchestration Tools  [[BR]]
+
+e)  Interfaces/Protocols Between Tools and Services  [[BR]]
+
+f)  Descriptor Schema and Registry Service  [[BR]]
+
+g)  Object Names and Registry Service  [[BR]]
+
+h)  XML Messaging Service  [[BR]]
+
+i)  Lookup Service  [[BR]]
+
+j)  Portal Service  [[BR]]
+
+k)  User Workspace and Archive Services  [[BR]]
+
+l)  Operational Services  [[BR]]
+
+m)  Services Shared by GIMI and GEMINI projects  [[BR]]
+
+n)  Support for Experimenters  [[BR]]
+
+o)  Support for Operators   [[BR]]
+
+
+These have been combined and summarized and shown in the sections below.  [[BR]]
+
+
+=== 4.2)  I&M Use Cases for Experiments, and Support for Experimenters  ===
+I&M Use Cases for Experiments  [[BR]]
+Support for Experimenters  [[BR]]
+
+1)  Definition of topic:  [[BR]]
+
+a)  How do we work towards Max Ott's vision for experiment support?  [http://groups.geni.net/geni/attachment/wiki/GEC12InstMeasWorkingSession/Will%20RSpec%20help%20us%20to%20do%20better%20science%20-%20GEC11%20-%20July%202011.pdf  slides] [[BR]]
+
+b)  Nominal experiment use case:  [[BR]]
+  1)  Setup and run experiment using Experiment Control Tools, Experiment Orchestration Service and Lab Portal.  [[BR]]
+  2)  Setup and run measurements using services within slice, and persistent services.  Option:  get measurement data from persistent MP.  [[BR]]
+  3)  Gather MD, and observe during experiment; formulate MDOD.  [[BR]]
+  4)  Archive MD with MDOD.  [[BR]]
+  5)  Share archived MD with others, per policy included within MDOD.  [[BR]]
+  6)  Pull MD out of archive, to analyze and/or visualize.  [[BR]]
+ 
+c)  What support must be provided for Experimenters?  how?  [[BR]] 
+
+2)  Who: Max Ott (NICTA);  Jim Griffioen (U Kentucky);  Prasad Calyam (Ohio Super Center);  Mike Zink (UMass Amherst) [[BR]]
+
+
+
+=== 4.3)  I&M Use Cases for Infrastructure Measurement, and Support for Operators ===
+I&M Use Cases for Infrastructure Measurement  [[BR]]
+Support for Operators   [[BR]]
+
+1)  Definition of topic:  [[BR]]
+
+a)  Delineate what infrastructure monitoring is and is not covered by this approach.  [[BR]]
+  1)  Yes:  monitoring of clusters/racks [[BR]]
+  2)  Yes:  passive measurements of transport switches, etc.  [[BR]]
+  3)  Yes:  active measurements of IP networks, of Layer 2 and OpenFlow paths [[BR]]
+
+
+b)  Nominal infrastructure measurement process:  [[BR]]
+  1)  Setup persistent or on-demand infrastructure measurement slice.  [[BR]]
+  2)  Make passive measurements or make active measurements.  [[BR]]
+  3)  Gather MD, and observe as it is gathered;  formulate MDOD.  [[BR]]
+  4)  Store MD in collector, describe with MDOD, and register MDOD so that MD can be shared.  [[BR]]
+  5)  Typically share MD with Aggregate Operator, GMOC and/or Experimenters, per policy written into MDOD.  [[BR]]
+  6)  Pull MD out of collector, analyze and visualize.  [[BR]]
+  7)  Archive MD with MDOD.  [[BR]]
+  8)  Share archived MD with others, per policy included within MDOD.  [[BR]]
+  9)  Pull MD out of archive, to analyze and/or visualize.   [[BR]]
+
+c)  What support must be provided for Operator?  how?  [[BR]]
+
+2)  Who: Martin Swany (Indiana U);  Eric Boyd (Internet2);  Jason Zurawski (Internet2);  Chris Small (Indiana U);  Ilia Baldine, for ExoGENI racks (RENCI);  ?, for InstaGENI racks (?)[[BR]]
+
+=== 4.4)  GENI Environment  ===
+Platform Targets  [[BR]]
+Experiment and Measurement Orchestration Tools  [[BR]]
+Interfaces/Protocols Between Tools and Services  [[BR]]
+
+1)  Definition of topic:  [[BR]]
+
+a)  Platform targets: [[BR]]
+  1)  protoGENI servers/VMs [[BR]]
+  2)  ORCA servers/VMs [[BR]]
+  3)  WiMAX sites [[BR]]
+  4)  ExoGENI (RENCI) racks;  like ORCA [[BR]]
+  5)  TransCloud (HP) racks;  like protoGENI? [[BR]]
+  6)  PlanetLab
+
+b) Experiment and Measurement Orchestration tools: [[BR]]
+  1)  FLACK [[BR]]
+  2)  GUSH (with Omni) [[BR]]
+  3)  SFACE + RAVEN [[BR]]
+
+c) Interfaces/protocols between tools and services: [[BR]]
+  1)  protoGENI API, with protoGENI RSpec v2, for resource assignment [[BR]]
+  2)  GENI AM API, with protoGENI RSpec v2, for resource assignment [[BR]]
+  3)  ns for topology [[BR]]
+  4)  ssh for image loading [[BR]]
+  5)  OMF messages for orchestration [[BR]]
+
+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);  Tom Mitchell (GPO);  Aaron Helsinger (GPO)  [[BR]]
+
+
+
+=== 4.5)  Descriptors, Objects and Registries, and Lookup Service  ===
+Descriptor Schema and Registry Service  [[BR]]
+Object Names and Registry Service  [[BR]]
+Lookup Service  [[BR]]
+
+1)  Definition of topic:  [[BR]]
+
+a)  MDOD schema, for XML file.  [http://groups.geni.net/geni/wiki/GEC11InstMeasWorkingSession#a2MeasurementDataObjectDescriptorMDOD  References]  [[BR]]
+
+b)  MDOD registry.  Use DOR registry? Include in iRODS? Consider IF-MAP server? [[BR]]
+
+c)  Object (e.g., I&M service) names.  [[BR]]
+
+d)  Object registry, with names and public key. [[BR]]
+
+e)  Home and global Lookup Service, as defined by perfSONAR  [[BR]]
+
+f)  Map MDOD into metadata that is registered  [[BR]]
+
+g)  Can Lookup Service be used for finding portals?  [[BR]]
+
+h)  Also Topology Service?  following UNIS?  [[BR]]
+
+2)  Who:  Jason Zurawski (Internet2);  Ezra Kissel (U Delaware);  Eric Boyd (Internet2);  Scott Jensen (Indiana U);  Larry Lannom (CNRI);  LEAD Giridhar Manepalli (CNRI);  Deniz Gurken (UH);  Aaron Helsinger (GPO)  [[BR]]
+
+
+
+=== 4.6)  Messaging Service ===
+XML Messaging Service  [[BR]]
+
+1)  Definition of topic:  [[BR]]
+
+a)  XMPP server, in public IP space.   Consider AMQP server?  Consider IF-MAP server? [[BR]]
+
+b)  Entities connect, and are authenticated.  [[BR]]
+
+c)  An entity may start a pub/sub node.  [[BR]]
+
+d)  When an entity subscribes, a message is sent to publisher requesting authorization.  [[BR]]
+
+e)  Use for OMF messages.  [[BR]]
+
+f)  Use for "event record messages".  [[BR]]
+
+2)  Who: Rudra Dutta (NCSU);  Shu Huang (RENCI);  Chirstoph Dwertmann (NICTA);  Martin Swany (IU);  Prasad Calyam (OSC);  Deniz Gurken (UH) [[BR]]
+
+
+=== 4.7)  Lookup Service ===
+Lookup Service  [[BR]]
+
+Note:  Merged into 4.5)  [[BR]]
+
+
+
+=== 4.8)  Portal Service ===
+Portal Service  [[BR]]
+
+1)  Definition of topic:  [[BR]]
+
+a) Towards Max Ott's vision for experiment support  [[BR]]
+
+b) Consider INSTOOLS portal service [[BR]]
+
+c) Define portal service for GIMI tools, with multiple functions. [[BR]]
+
+d) How are partitions for different users managed? [[BR]]
+
+e) Can these portal services be merged? 
+
+f) Are these portal services really a combination of gateway and user workspace services?[[BR]]
+
+2)  Who: Jim Griffioen or ? (U Kentucky);  Christoph Dwertmann (NICTA);  Jason Zurawski, for NetKarma (Internet2) [[BR]]
+
+
+=== 4.9)  User Workspace and Archive Services ===
+User Workspace and Archive Services  [[BR]]
+
+1)  Definition of topic:  [[BR]]
+
+a)  Consider CNRI prototype user workspace and archive service [[BR]]
+
+b)  Consider U Kentucky archive service [[BR]]
+
+c)  Consider 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]]
+
+2)  Who: Giridhar Manepalli (CNRI);  Shu Huang (RENCI) ;  Larry Lannom (CNRI);  Wesley Wu (U Kentucky) [[BR]]
+
+
+=== 4.10 Operational Services ===
+Persistent Operational Services  [[BR]]
+Services Shared by GIMI and GEMINI  [[BR]]
+
+1)  Definition of topic:  [[BR]]
+
+a)  What persistent operational services must be supported: [[BR]]
+  1)  Descriptor registry.  DOR?  iRODS? IF-MAP? [[BR]]
+  2)  Object registry.  DOR? [[BR]]
+  3)  XML messaging service [[BR]]
+  4)  Home and global Lookup Services;  also Topology Service?  UNIS?  [[BR]]
+  5)  INSTOOLS portal service [[BR]]
+  6)  GIMI portal service [[BR]]
+  7)  U Kentucky archive service [[BR]]
+  8)  CNRI prototype user workspace and archive service [[BR]]
+  9)  iRODs archive service [[BR]]
+
+b)  What services can be shared by GIMI and GEMINI tools? [[BR]]
+
+c)  How do these relate to other GENI services/functions, including clearinghouse?
+
+2)  Who: Mike Zink (UMass Amherst);  Martin Swany (Inidana U);  Jim Griffioen (U Kentucky);  Giridhar Manepalli (CNRI);  Aaron Helsinger (GPO)   [[BR]]