Changes between Version 27 and Version 28 of GEC14Agenda/IMDesignTopics


Ignore:
Timestamp:
06/28/12 09:23:41 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC14Agenda/IMDesignTopics

    v27 v28  
    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]]
     150 * Define, prototype, deploy and operate a GENI User Workspace. [[BR]]
    151151 * 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.
     152 * So that the GENI User Workspacet can be hosted on a server dedicated to the user (even the user's laptop), provide on a portable VM.  [[BR]]
     153 * Use the "GENI User Workspace" to test the GIMI and GEMINI tools, and during their tutorials.  [[BR]]
    154154
    155155Summary  [[BR]]
     
    157157 * Current configuration (Spiral 4)  [[BR]]
    158158 * Next configuration (Spiral 5)  [[BR]]
     159
     160Discussion  [[BR]]
     161 * Should the GENI User Workspace be supported on a server hosting multiple user workspaces for multiple users?  [[BR]]
     162 * Which tools should be added to the GENI User Workspace?  [[BR]]
     163 *  How can we best optimize "user tools" and their interfaces to better meet the needs of GENI users (e.g., experimenters and operators).  [[BR]]
     164
     165
    159166
    160167=== T5)  Descriptors, Objects and Registries  ===
     
    206213 * [wiki:InstMeasTopic_4.6MessagingService  work in progress]  [[BR]]
    207214 * An XMPP server is operational at Rutgers WINLAB (and other GENI wireless sites) for OMF messages.  [[BR]]
    208  * An XML messaging service has been prototyped by the IMF project.  [  slides] (see also I&M and Monitoring session at GEC14) [[BR]]
     215 * An XML messaging service has been prototyped by the IMF project.  [  slides] [[BR]]
    209216 * An XMPP server has been setup at UMass Amherst.  [[BR]]
    210217 * Current configuration  [  slides]  [[BR]]
     
    247254 * How is persistent object identifier (i.e., handle) generated?  also registered?  and later resolved?  Include necessary Object Identifier (OI) service.[[BR]]
    248255 * How are partitions for different users managed? [[BR]]
     256 * How is authorization for a user done?  [[BR]]
    249257 * How is data in MDOD used to set archive sharing policy?  what is required in MDOD? [[BR]]
    250  * Will the GEMINI project want to use the iRODS service?  [[BR]]
     258 * How will the GEMINI project use the iRODS service?  [[BR]]
    251259 * Will other parts of GENI want to use the iRODS service?  [[BR]]
    252260 * Do we need a breakout session for further discussion?  when?  [[BR]]
     
    2552639:20am [[BR]]
    256264
    257 Christoph Dwertmann (NICTA) [[BR]]
     265Christoph Dwertmann (NICTA) and Cong Wang (UMass Amherst) [[BR]]
    258266
    259267Tasks
     
    316324 * Will you refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances? [[BR]]
    317325 * What additional features are under consideration?  [[BR]]
     326 * What new interfaces are under consideration?  [[BR]]
    318327 * Will the GIMI project want to use the UNIS service?  [[BR]]
    319328 * Will other parts of GENI want to use the UNIS service, e.g., stitching?  [[BR]]
     
    333342 * Bugs must be gathered, tracked and fixed by GIMI team;  final acceptance test will be performed by the GPO  (who is lead?)  [[BR]]
    334343 * Bugs must be gathered, tracked and fixed by GEMINI team;  final acceptance test will be performed by the GPO   (who is lead?) [[BR]]
    335  * Feature requests must be gathered, tracked and evaluated by GIMI and GEMINI team  (who is lead?)  [[BR]]
    336  * Feature requests must be gathered, tracked and evaluated by GIMI and GEMINI team  (who is lead?)  [[BR]]
     344 * Feature requests must be gathered, tracked and evaluated by GIMI team  (who is lead?)  [[BR]]
     345 * Feature requests must be gathered, tracked and evaluated by GEMINI team  (who is lead?)  [[BR]]
    337346
    338347 * v1.1 of GIMI tools must be released by GEC15, including bug fixes and new features, fully tested and ready for day-to-day use  (who is lead?)   [[BR]]
    339348 * v1.1 of GEMINI tools must be released by GEC15, including bug fixes and new features, fully tested and ready for day-to-day use  (who is lead?)   [[BR]]
    340349
     350 * User Worksapce should be readily available to users, with bug fixes and new features.  (Jeanne Ohren)  [[BR]]
    341351 * XML messaging service should provide agreed-upon features, and be reliably operational  (who is lead?)    [[BR]]
    342352 * iRODS archive service should provide agreed-upon features, and be reliably operational  (who is lead?)  [[BR]]
     
    348358Discussion
    349359 * Do we have leads identified for all items?  [[BR]]
    350  * How should user workspace be supported?  on a VM?  on a dedicated server?   [[BR]] 
    351  
    352360
    353361