wiki:GEC16Agenda/ServiceDevelopersRoundtable

Service Developers Roundtable at GEC16

Tuesday, March 19, 8:30am - 10am
Room: City Creek
Session leader: Harry Mussman (GENI Project Office, Raytheon BBN Technologies)

Description

This session will focus on the evolution of tools and services to allow GENI to work towards a "unified experiment environment".

The discussion topics are:

  • Future of graphical resource assignment tools
  • Integration of portals and all tools with graphical interfaces
  • Introduction of the OMF to configure and orchestrate Instrumentation and Measurement (I&M) services and the experimenter's application services

In each case, we will start with a review of current tools and services, and then have a round-table discussion of possible next steps towards a “unified experiment environment”.

It is hoped that the discussions at this session may inspire proposals that will be submitted to GENI Solicitation 4.

Finally, we will form teams to continue the discussions.

Pre-Requisites

None

Agenda

This is a tentative agenda, which may change.

1) Introductions

8:30am

2) Future of graphical resource assignment tools

8:35am

Introduction

Harry Mussman (GPO)

GENI experiment management Step 3: Obtain slice, install software

  • Now: ExoGENI experimenter typically using Flukes to obtain slice, load images/pkgs
  • Now: InstaGENI experimneter typically using FLACK to obtain slice, load images/pkgs
  • Next: move towards common graphical resource assignment tool(s) for both ExoGENI and InstaGENI racks

Current GENI CH Portal

Tom Mitchell (GPO)
5min

slides: current config; current capabilities and issues; future possibilities

Now: good introductory tool, for inexperienced experimenter

Current FLACK tool

Matt Strum and Rob Ricci (Univ Utah)
5min

slides: current config; current capabilities and issues; future possibilities

New: other tools can include FLACK
New: plug-in to add GEMINI tools
New: better error handling
Soon: AM API v3

Current Flukes tool

Victor Orlikowski (Duke)
5min

slides: current config; current capabilities and issues; future possibilities

Now: used with ExoGENI, with ndl
New: extend duration of a slice
New: save manifest and request into iRODS

Roundtable discussion

Tom Mitchell (GPO); Victor Orlikowski (Duke); Rob Ricci (or Matt Strum) (Univ Utah); Niky Riga (GPO)
15min
How do we move towards common graphical resource assignment tool(s) for both ExoGENI and InstaGENI racks?

Conclusions:

1) FLACK works with InstaGENI, now using AM API

2) Need to test FLACK with ExoGENI using AM API; may have issue with accepting certificate

3) FLUKES has been designed for ORCA API, and would be difficult to adapt to AM API (for use with InstaGENI)

4) However, could use FLUKES to setup slice in ExoGENI rack using ORCA API, and then retrieve manifest rspec following AM API

Issues:

5) Can draw a bigger topology than can be realized; not sure this can be fixed at drawing time, only after first submission of request; however, could consider "beginner's mode", which would limit drawing topology

Team to continue discussion:

Tom Mitchell (GPO); Victor Orlikowski (Duke); Ilia Baldine (RENCI); Rob Ricci and Matt Strum (Univ Utah); Niky Riga (GPO)

3) Integration of portals and all tools with graphical interfaces

9:05am

Introduction

Harry Mussman (GPO)

GENI experiment management Step 2: Establish exper mgmt environment

  • Next: GENI CH Portal, to establish credentials, and enter GENI

GENI experiment management Step 3: Obtain slice, install software

  • Now: ExoGENI typically using Flukes to obtain slice, load images/pkgs
  • Now: InstaGENI typically using FLACK to obtain slice, load images/pkgs
  • Next: move towards common graphical resource assignment tool for both ExoGENI and InstaGENI racks

GENI experiment management Step 5: Run/orchestrate Instrumentation and Measurement (I&M) services and the experimenter's application services

  • Now: GEMINI I&M tools use portal to GUI, to config/orchestrate and present graphs
  • Now: GIMI I&M tools use portal to GUI, to config/orchestrate and present graphs

GENI experiment management Step 6: Analyze

  • Now: Both use portal on GENI Storage Service (iRODS) to curate files (objects)

Next: Integration of portals and all tools with graphical interfaces, to better unify experiment environment

Current GENI CH Portal

Tom Mitchell (GPO)
5min

slides: current config; current capabilities and issues; future possibilities

Now: have embedded FLACK

Current GEMINI Portal (GENI Desktop)

Hussam Nasir (Univ Kentucky)
5min

slides: current config; current capabilities and issues; future possibilities

Now: login using emulab or protoGENI account
Now: provides access to your slice
Now: auto login to FLACK to create slice
Now: built as HTML5 web page with plug-ins

Current GIMI Portal/GUI

Mike Zink (UMass Amherst)
5min

Current config; current capabilities and issues; future possibilities

link to GIMI portal

Now: based on Lab wiki, with 3 windows for plan, script, results

Roundtable discussion

Tom Mitchell (GPO); Hussam Nasir (Univ Kentucky); Mike Zink (UMass Amherst); Jeanne Ohren (GPO)
15min

How to we move towards integration of portals and all tools with graphical interfaces, to better unify experiment environment?

Strawman:

  • Consider single sign-on at GENI CH portal,
  • link to common graphical resource assignment tool(s), ot obtain slice
  • then link to GEMINI Portal (GENI Desktop) for entry into I&M tools,
  • then link to I&M GUIs (including the GEMINI GUI, GIMI portal/GUI and the iRODS portal/GUI)

Conclusions:

1) Be flexible in use of tools; don't kill innovation

2) Push towards single-sign-on

3) To make it easier to mix and match tools. pass info from tool to tool, using iRODS as a repository

Issues:

Team to continue discussion:

Tom Mitchell (GPO); Hussam Nasir (Univ Kentucky); Mike Zink (UMass Amherst); Jeanne Ohren (GPO)

4) Introduction of OMF to config/orchestrate I&M and experimenter's application services

9:35am

Introduction

Harry Mussman (GPO)

Step 5: Run/orchestrate I&M and experimenter's application services

  • Now: GEMINI uses portal to GUI, to config/orchestrate
  • Now: GIMI uses OMF EC with Ruby script to config/orchestrate
  • Gap: no common way to config/orchestrate exp apps
  • Next: Integrate orchestration of all services, including GIMI, GEMINI and experimenter's application services, to better unify experiment environment
  • Suggest: Introduce OMF for config/orchestration of all I&M tools and experimenter's application services; later, add optional graphical interface

Summary of OMF capabilities

Max Ott (NICTA)
10min

slides: current config; current capabilities and issues; future possibilities

Roundtable discussion

Max Ott (NICTA); Marshall Brinn (GPO); Martin Swany (Indiana Univ); Fraida Fund (NYU Poly)
15min

Should we introduce OMF into GENI for config/orchestration of all I&M tools and experimenter's application services?

Conclusions:

1) Use of OMF good for repetitive experiments

2) Also use of OMF good for predefined experiments, such as thsoe used in classrooms

3) Use of OMF essential for large experiment 100s or 100s of nodes

4) But, how to introduce use of OMF for "middle range" of experiments?

  • Per GIMI approach, introduce OMF RC (resource controller) in images
  • Show a "clean path" from just using ssh to the use of OMF

Issues:

Team to continue discussion:

Max Ott (NICTA); Marshall Brinn (GPO); Martin Swany (Indiana Univ); Rob Ricci (Univ Utah); Mike Zink (UMass Amherst); Fraida Fund (NYU Poly)

5) Adjourn

10am

Last modified 7 years ago Last modified on 03/28/13 10:51:50

Attachments (7)