Changes between Version 13 and Version 14 of GEC14Agenda/IMDesignTopics


Ignore:
Timestamp:
06/26/12 11:28:40 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC14Agenda/IMDesignTopics

    v13 v14  
    5555* First focus: I&M use cases for experiments, with default OML Client in nodes that gathers passive measurements like INSTOOLS, and provides basic node-to-node connectivity tests using ping and iperf  [[BR]]
    5656* Second focus:  I&M use cases for infrastructure measurement  [[BR]]
    57 * Later focuse:  add sensor measurement data, carried in data network  [[BR]]
     57* Later focus:  add sensor measurement data, carried in data network  [[BR]]
    5858
    5959* Spiral 4 supported aggregates:  ORCA servers/VMs and ExoGENI (RENCI) racks  [[BR]]
     
    6262
    6363* Introduces XML messaging service, with pub/sub, in public IP space    [[BR]]
    64 * Introduces iRODS service, for measurement data archive.  [[BR]]
     64* Introduces iRODS service, as a measurement data archive.  [[BR]]
    6565* Introduces IREEL portal service, for measurement data analysys and presentation.  [[BR]]
    6666
     
    104104* Spiral 5 supported aggregates:  ORCA servers/VMs and ExoGENI (RENCI) racks  [[BR]]
    105105
    106 * Continue INSTOOLS portal service, to find GUIs    [[BR]]
    107 * Continue LAMP local and global Unified Network Information Service (UNIS), to register available measurement data, and network topology  [[BR]]
    108 
    109 Martin Swan will review:  [[BR]]
     106* Continues INSTOOLS portal service, to find GUIs    [[BR]]
     107* Continues LAMP local and global Unified Network Information Service (UNIS), to register available measurement data, and network topology  [[BR]]
     108
     109Martin Swany will review:  [[BR]]
    110110
    111111* Current architecture, design and status. [[BR]]
     
    129129 User tools for experiment and measurement setup and orchestration [[BR]]
    130130 Interfaces/protocols between user tools and GENI aggregates  [[BR]]
    131  Supported GENI aggregtaes  [[BR]]
     131 Supported GENI aggregates  [[BR]]
    132132
    133133Summary  [[BR]]
     
    143143 Work towards Max Ott's vision for experiment support  [[BR]]
    144144 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]]
    145  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]]
     145 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]]
    146146 These services should work together via APIs, etc., to streamline the experiment process. [[BR]]
    147147
     
    150150 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]]
    151151 2)  Multiple GENI User Tools, where each provides a service with an interface or a "portal" to the user. [[BR]]
    152 
    153152 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]]
    154  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]]
     153 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]]
    155154 Optimize "user tools" and their interfaces to better meet the needs of GENI users (e.g., experimenters and operators).  [[BR]]
    156155 Use the "GENI User Workspace" to test the GIMI and GEMINI tools, and during their tutorials.
     
    169168 Want to extend MDOD to cover all types of objects, i.e., software images.  (NetKarma)[[BR]]
    170169 Want to use MDOD schema to define Event Record schema.  (NetKarma)[[BR]]
    171  Do we need MDOD registry?  Use UNIS lookup service?  Use DOR registry? Include in iRODS? [[BR]]
     170 Do we need MDOD registry?  Use UNIS lookup service? Include in iRODS? [[BR]]
    172171 Need MDOD creation and editing service. (who?) [[BR]]
    173172 Need Measurement Data Object identifiers (names);  sometimes need a persistent, public reference;  consider DataCite approach, which uses handle  [[BR]]
    174 
    175 [wiki:InstMeasTopic_4.5DescriptorsObjectsRegistriesLookupService  Work in Progress]  [[BR]]
    176173
    177174
     
    227224
    228225Next steps
    229  Who will review?
     226 Who will review?  Shall we have a breakout meeting on Wed, 7/11?
    230227 Who will implement?
    231228 How will this be included into iRODS?