Changes between Version 40 and Version 41 of InstMeasTopic_4.8PortalService


Ignore:
Timestamp:
02/16/12 17:45:13 (7 years ago)
Author:
hmussman@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • InstMeasTopic_4.8PortalService

    v40 v41  
    22
    33
    4 = 4.8)  "GENI User Portal" Design Topic =
    5 
    6 ==  4.8.1)  Goals ==
    7 
    8   Provide a first-order definition of the "GENI User Portal", combining the capabilities of the various "portal services" that have been implemented to date, so that GENI I&M users can use the "GENI User Portal" when they conduct experiments or instrument infrastructure.
    9 
    10 == 4.8.2)  Team ==
     4= 4.8)  GENI User Portal Services =
     5
     6== 1)  Goals ==
     7
     8 Work towards Max Ott's vision for experiment support  [[BR]]
     9
     10    [http://groups.geni.net/geni/attachment/wiki/InstMeasTopic_4.8PortalService/Paper_-_Tridentcom.pdf  TridentCom Portal Paper][[BR]]
     11
     12    [http://groups.geni.net/geni/attachment/wiki/InstMeasTopic_4.8PortalService/Will%20RSpec%20help%20us%20to%20do%20better%20science%20-%20GEC11%20-%20July%202011.pdf  Vision Slides from GEC11]   [[BR]]
     13
     14    [http://omf.mytestbed.net/projects/omf/wiki/PortalDesignSystemRequirements#Overview  Testbed Portal System Requirements]  [[BR]]
     15 
     16    [http://groups.geni.net/geni/attachment/wiki/InstMeasTopic_4.8PortalService/Requirements-2.1.pdf  Redmine Portal Service  ]  [[BR]]
     17
     18    [[Image(NICTALabNotebookServiceModel.jpg, 70%)]]  [[BR]]
     19
     20    [[Image(SystemCLI.jpg, 50%)]]  [[BR]]
     21
     22    [[Image(NICATRedminePortalTool.jpg, 40%)]]  [[BR]]
     23 
     24    NICTA Lab Notebook Service capabilities [[BR]]
     25    – Wiki: Keep notes with references[[BR]]
     26    – Schedule & monitor runs[[BR]]
     27    – Analysis with integrated R server[[BR]]
     28    – Repository for all artifacts[[BR]]
     29
     30 Provide a way for a GENI user (e.g., experimenter) to access a wide variety of "GENI User Portal Services", where each portal service provides an interface (e.g., API or GUI) to the user. [[BR]]
     31
     32 Together, the "GENI User Portal 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]]
     33
     34 These services should work together via APIs, etc., to streamline the experiment process. [[BR]]
     35
     36==  2)  Tasks ==
     37
     38 Based upon the configuration defined below, the implementation is split into: [[BR]]
     39
     40 1)  GENI User Workspace Service, which is a persistent Linux OS environment, that serves as a container for multiple portal tools [[BR]]
     41
     42 2)  Multiple GENI User Portal Tools, where each provides an interface or "portal" to the user. [[BR]]
     43
     44 Define, prototype, deploy and operate a GENI User Workspace Service. [[BR]]
     45
     46 Gather the various "portal services" 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]]
     47
     48 Optimize "portal services" and their interfaces to better meet the needs of GENI users (e.g., experimenters and operators).  [[BR]]
     49
     50== 3)  Team ==
    1151 
    1252  Jim Griffioen and/or Charles Carpenter (INSTOOLS and GEMINI, U Kentucky)  [[BR]]
     
    1757  Harry Mussman  (GPO) [[BR]]
    1858
    19 == 4.8.3)  Meetings ==
    20 
    21 == 4.8.4)  Vision ==
    22 
    23   Towards Max Ott's vision for experiment support  [[BR]]
    24 
    25     [http://groups.geni.net/geni/attachment/wiki/InstMeasTopic_4.8PortalService/Paper_-_Tridentcom.pdf  TridentCom Portal Paper][[BR]]
    26 
    27     [http://groups.geni.net/geni/attachment/wiki/InstMeasTopic_4.8PortalService/Will%20RSpec%20help%20us%20to%20do%20better%20science%20-%20GEC11%20-%20July%202011.pdf  Vision Slides from GEC11]   [[BR]]
    28 
    29     [http://omf.mytestbed.net/projects/omf/wiki/PortalDesignSystemRequirements#Overview  Testbed Portal System Requirements]  [[BR]]
    30  
    31     [http://groups.geni.net/geni/attachment/wiki/InstMeasTopic_4.8PortalService/Requirements-2.1.pdf  Redmine Portal Service  ]  [[BR]]
    32 
    33     [[Image(NICTALabNotebookServiceModel.jpg, 70%)]]  [[BR]]
    34 
    35     [[Image(SystemCLI.jpg, 50%)]]  [[BR]]
    36 
    37     [[Image(NICATRedminePortalTool.jpg, 40%)]]  [[BR]]
    38  
    39     NICTA Lab Notebook Service capabilities [[BR]]
    40     – Wiki: Keep notes with references[[BR]]
    41     – Schedule & monitor runs[[BR]]
    42     – Analysis with integrated R server[[BR]]
    43     – Repository for all artifacts[[BR]]
    44 
     59== 4)  Meetings ==
     60
     61
     62== 5)  Issues ==
     63
     64
     65
     66== 6)  GENI User Workspace Service:  Configuration  ==
     67
     68[[Image(Visio-112811_UseCases_Projects_Figures_Page_05.jpg, 90%)]]  [[BR]]
     69
     70Linux OS environment: [[BR]]
     71 - On server: [[BR]]
     72   - Dedicated to user, i.e., a desktop server [[BR]]
     73   - In an organization (e.g., BBN), shared by multiple users in the organization [[BR]]
     74   - In GENI infrastructure, shared by multiple users [[BR]]
     75     - How are partitions for different users assigned?  using GENI resource assignment process? [[BR]]
     76 – With login for the user [[BR]]
     77   - Includes file system [[BR]]
     78   – Includes certificate and credential stores [[BR]]
     79   – Includes various services/tools dedicated to this user, with programmatic and web interfaces [[BR]]
     80     - With interfaces/APIs between services tools [[BR]]
     81     - See Testbed Portal System Requirements above for an example [[BR]]
     82     - Prefer programmatic interface/API to allow coordination between services, and scripts [[BR]]
     83     - Prefer web interfaces to allow users to view topology, measurement data, events and trends [[BR]]
     84
     85Included services/tools/capabilities: [[BR]]
     86 - User can load desired services/tools, and bind them together [[BR]]
     87 - Experiment Control services/tools (e.g., GUSH, OMNI, OMF Experiment Controller) used to: [[BR]]
     88   - Assign resources for application and I&M services [[BR]]
     89   - Load topology and load images into slice, including those required for I&M [[BR]]
     90   - Configure and orchestrate/manage experiment applications  [[BR]]
     91   - Configure and orchestrate/manage I&M services  [[BR]]
     92 - Measurement Data Object Descriptor (MDOD) creation and editing, including annotation [[BR]]
     93 - User Workspace (UW) service [[BR]]
     94 - Measurement Collection (MC) service [[BR]]
     95 - Measurement Analysis and Presentation (MAP) services [[BR]]
     96 - Topology Presentation service [[BR]]
     97 - What specific services/tools will be available?  [[BR]]
     98
     99NOT included services/tools: [[BR]]
     100 - Shared archive service, i.e., iRODS service [[BR]]
    45101
    46102