wiki:InstMeasTopic_4.8PortalService

Version 35 (modified by hmussman@bbn.com, 7 years ago) (diff)

--

4.8) GENI User Portal Design Topic

4.8.1) Goals

Provide a first-order definition of a "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.

4.8.2) Team

Jim Griffioen and/or Charles ? (INSTOOLS and GEMINI, U Kentucky)
Max Ott and/or Christoph Dwertmann (NICTA)
Chris Small (NetKarma, IU)
Ahmed El-Hassany (IU)
Jeanne Ohren (GPO)
Harry Mussman (GPO)

4.8.3) Meetings

4.8.4) Vision

Towards Max Ott's vision for experiment support

TridentCom Portal Paper

Vision Slides from GEC11

Testbed Portal System Requirements

Redmine Portal Service




NICTA Lab Notebook Service capabilities
– Wiki: Keep notes with references
– Schedule & monitor runs
– Analysis with integrated R server
– Repository for all artifacts

4.8.4) Current and Planned Portal Services

a) INSTOOLS portal and web services (U Kentucky)

INSTOOLS project wiki

slides

design document

INSTOOLS tutorial

INSTOOLS evaluation


INSTOOLS Portal service capabilities:

  • Resident in browser, with FLACK experiment control tool
  • Provides a way for experimenter to find all web servers in experimenter's slice
  • Allows experimenter to move data to archive service (local (U Kentucky) or remote (CNRI)

INSTOOLS Web service capabilities:

  • One is resident in each Measurement Controller (MC)
  • Allows experimenter to configure measurements
  • Allows experimenter to view topology and view measured data
  • Allows experimenter to open a command line into any node, using vnc protocol

b) LAMP Periscope services (U Delaware+)

LAMP project wiki

LAMP tutorial

LAMP evaluation


Periscope services capabilities:

  • Slice Overview
    • Configuration Status
    • Registered Services
      • Measurement Tools (Daemons)
      • perfSONAR Services
  • Configuration
    • Enabled Services
    • Clock Synchronization
    • Scheduled Tests
  • Visualization
    • Throughput
    • One-way Latency
    • Ping Latency
    • Host Monitoring

c) Measurement Data Archive services (CNRI)

Measurement Data Archive (MDA) service capabilities:

  • The MDA srvc allows users to store, retrieve, browse, search, share and archive measurement data files, including their associated metadata.
  • The MDA srvc is not limited to measurement data, and can be used for other types of files needed by a researcher.
  • The MDA srvc utilizes the mechanisms provided by the CF to authenticate and authorize users.
  • The MDA srvc is implemented by a User Workspace (UW) Srvc, which in turn utilizes an Digital Object Archive (DOA) Srvc.



Design of prototype MDA service

Prototype MDA web interface

Programmatic Linux OS interface to User Workspace service:

  • Users have accounts
  • Users can mount file system using SMB (Samba) protocol
  • Users may securely transfer files using SFTP
  • Users can access a secure shell (SSH) to modify permissions and group settings.

Web interface to User Workspace service:

  • Data objects can be searched, browsed and retrieved using web front end
  • Data objects can be found using keywords or timestamps
  • Users may examine metadata for a data object
  • Users may download data or metadata
  • Users may request that an object be sent to the persistent archive service; a persistent identifier is returned

Web interface to Object Archive service:

  • Data objects can be searched, browsed and retrieved using web front end

Programmatic HTTP interface to User Workspace service:

  • Uses may GetID
  • Users may Archive an object
  • Users may retrieve an object or metadata

Programmatic HTTP interface to Object Archive service:

  • Uses may GetID
  • Users may retrieve an object or metadata

d) NICTA Lab Notebook services

Testbed Portal System Requirements

Redmine Portal Service


Image (SystemCLI.jpg, 50%)?


NICTA Lab Notebook Service capabilities
– Wiki: Keep notes with references
– Schedule & monitor runs
– Analysis with integrated R server
– Repository for all artifacts

e) GIMI Portal services


Experiment Control service capabilities:
– Assign resources to slice, including those required for I&M
– Load topology and load images into slice, including those required for I&M

  • Orchestrate (manage) experiment applications (processes)

Measurement Orchestration (MO) service capabilities:
– Orchestrate (manage) I&M services
– Create and edit Measurement Data Object Descriptor (MDOD), including annotation

OML Server and Results service capabilities:
– Collect data (MC function)
– Analyze and Present data (MAP functions)

  • Web interface
  • pdf file output

– Archive or retrieve SQL data object to iRODS archive service

f) GEMINI Portal services

Expected to include some or all of:

  • LAMP Periscope services
  • INSTOOLS Portal service
  • INSTOOLS web service
  • more?

4.8.5) GENI User Portal Definition

Basic configuration

Partitions for different users; how are they managed? can they be assigned to users using WINLAB login service?
Are these portal services really a combination of gateway and user workspace services, with various available tools?

Summary of portal services use cases (Jeannie Ohren, GPO)

Portal services use cases

– User’s window into GENI
– Conveniently and easily manage GENI resources, I&M data, and experiment results
– A place to control the experiment
– Works for both short/small (weeks-months?) and long/large (months-years?) experiments
– MAP (Measurement, Analysis, Presentation)
– A place to store and retrieve experiment results and analysis (Lab book?)
– Largely stateless? (Does this conflict with 4?)
– A way to get to necessary GENI experimenter tools such as Flack, GUSH, OMNI
– Manages moving I&M data to archive (iRODS?) with metadata (MDOD?)
– Allows the public to access published experiment results

Attachments (19)