wiki:GEC16Agenda/ServiceDevelopersRoundtable

Version 22 (modified by hmussman@bbn.com, 11 years ago) (diff)

--

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 possible next steps towards a “unified experiment environment”.

Finally, we will form teams to continue the discussion.

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

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

Current FLACK tool

(Rob Ricci) (Univ Utah)
5min

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

Current Flukes tool

(Ilia Baldine) (RENCI)
5min

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

Roundtable discussion

Tom Mitchell (GPO); (Ilia Baldine) (RENCI); (Rob Ricci) (Univ Utah); Niky Riga (GPO)
15min

How do we move towards common graphical resource assignment tool(s) for both ExoGENI and InstaGENI racks?

What can we learn from current tools?

What capabilities are required? desirable?

Can we adapt a current tool? or do we need a new tool? or multiple new tools?

Is there new technology that should be used?

[Any additional topics, suggestions and issues suggested by members of roundtable?]

At the end:

  • List of conclusions
  • List of issues
  • Team to continue discussion

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
  • Now: GEMINI I&M tools use portal to GUI, to configure and present graphs
  • Now: GIMI I&M tools use portal including GUI, to configure 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

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

Current GEMINI Portal (GENI Desktop)

Hussam Nasir (Univ Kentucky)
5min

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

Current GIMI Portal/GUI

(Mike Zink) (UMass Amherst)
5min

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

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?

What features are required? desirable?

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 GIMI portal/GUI and the iRODS portal/GUI)

[Any additional topics, suggestions and issues suggested by members of roundtable?]

At the end:

  • List of conclusions
  • List of issues
  • Team to continue discussion

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

5 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?

What are advantages?

What are current limitations that need to be fixed?

Could we add a graphical interface?

[Any additional topics, suggestions and issues suggested by members of roundtable?]

At the end:

  • List of conclusions
  • List of issues
  • Team to continue discussion

5) Adjourn

10am

Attachments (7)