Version 16 (modified by, 8 years ago) (diff)


4) GENI I&M Design Topics


These are the GENI I&M priority design topics that must be resolved to allow the current GENI I&M projects to proceed, particularly the large Sol 3 project (GIMI and GEMINI)

These topics were identified and reviewed at the GEC12 I&M meeting


Resolve between now (GEC12) and GEC13.

Simplify where possible!


Form teams for each topic, and identify a LEAD for each topic. [[BR]

Teams should meet by confernce call, or in person, and complete a report for presentation at GEC13.

4.1) List of All Identified Topics


a) I&M Use Cases for Experiments
b) I&M Use Cases for Infrastructure Measurement
c) Platform Targets
d) Experiment and Measurement Orchestration Tools
e) Interfaces/Protocols Between Tools and Services
f) Descriptor Schema and Registry Service
g) Object Names and Registry Service
h) XML Messaging Service
i) Lookup Service
j) Portal Service
k) User Workspace and Archive Services
l) Operational Services
m) Services Shared by GIMI and GEMINI projects
n) Support for Experimenters
o) Support for Operators

These have been combined and summarized and shown in the sections below.

4.2) I&M Use Cases for Experiments, and Support for Experimenters

I&M Use Cases for Experiments
Support for Experimenters

Work in Progress

1) Goals

From Sec. 2 of the GENI I&M Architecture document:

To conduct useful and repeatable experiments, GENI experimenters require extensive and reliable instrumentation and measurement capabilities to gather, analyze, present and archive Measurement Data (MD).

Remove the burden on researcher to become a system and network measurement infrastructure expert so that researcher can better focus on the science in the experiments

Work towards Max Ott's vision for experiment support


Define use cases for a wide range of experiments: complex (by skilled experimenters) to simple (by novice experimenter, i.e., a student)

2) Tasks

Provide a concise but complete definition of I&M Use Cases for Experiments

Identify the support that should be available to experimenters, i.e., on-line instructions, examples and help desks.

Update the GENI I&M Architecture document:

Sec. 3.1. I&M Use cases for Experimenters
Sec. 4.2.1 Typical Arrangements of I&M Services: For Experimenter Gathering MD from their Slice
Sec. 4.3.1 Type 1 I&M Service: Service Contained within a Slice

Use as guidance in the design of GENI I&M tools, particularly for the GEMINI and GIMI projects

3) Team

CO-LEAD Jim Griffioen (U Kentucky)
Hussamuddin Nasir (U Kentucky)
CO-LEAD Mike Zink (UMass Amherst)
David Irwin (UMass Amherst)
Max Ott (NICTA)
Prasad Calyam (Ohio Super Center)
Harry Mussman (GPO)

4.3) I&M Use Cases for Infrastructure Measurement, and Support for Operators

I&M Use Cases for Infrastructure Measurement
Support for Operators

Work in Progress

1) Definition of topic:

a) Delineate what infrastructure monitoring is and is not covered by this approach.

1) Yes: monitoring of clusters/racks
2) Yes: passive measurements of transport switches, etc.
3) Yes: active measurements of IP networks, of Layer 2 and OpenFlow paths

b) Nominal infrastructure measurement process:

1) Setup persistent or on-demand infrastructure measurement slice.
2) Make passive measurements or make active measurements.
3) Gather MD, and observe as it is gathered; formulate MDOD.
4) Store MD in collector, describe with MDOD, and register MDOD so that MD can be shared.
5) Typically share MD with Aggregate Operator, GMOC and/or Experimenters, per policy written into MDOD.
6) Pull MD out of collector, analyze and visualize.
7) Archive MD with MDOD.
8) Share archived MD with others, per policy included within MDOD.
9) Pull MD out of archive, to analyze and/or visualize.

c) What support must be provided for Operator? how?

2) Who: LEAD Martin Swany (Indiana U); Eric Boyd (Internet2); Jason Zurawski (Internet2); Prasad Calyam (Ohio Super Center); Chris Small (Indiana U); Ilia Baldine, for ExoGENI racks (RENCI); ?, for InstaGENI racks (HP); ?, for GMOC

4.4) GENI Environment

Platform Targets
Experiment and Measurement Orchestration Tools
Interfaces/Protocols Between Tools and Services

Work in Progress

1) Definition of topic:

a) Platform targets:

1) protoGENI servers/VMs
2) ORCA servers/VMs
3) WiMAX sites
4) ExoGENI (RENCI) racks; like ORCA
5) TransCloud (HP) racks; like protoGENI?
6) PlanetLab

b) Experiment and Measurement Orchestration tools:

2) GUSH (with Omni)

c) Interfaces/protocols between tools and services:

1) protoGENI API, with protoGENI RSpec v2, for resource assignment
2) GENI AM API, with protoGENI RSpec v2, for resource assignment
3) ns for topology
4) ssh for image loading
5) OMF messages for orchestration

2) Who: Martin Swany (IU); Jim Griffioen (U Kentucky); Ilia Baldine, for ExoGENI racks (RENCI); ?, for InstaGENI racks (?); David Irwin (UMass Amherst); Mike Zink (UMass Amherst); Christoph Dwertmann (NICTA); LEAD Harry Mussman (GPO); Tom Mitchell (GPO); Aaron Helsinger (GPO); Marshall Brinn (GPO); Vic Thomas (GPO)

4.5) Descriptors, Objects and Registries

Descriptor Schema and Registry Service
Object Names and Registry Service

Work in Progress

1) Definition of topic:

a) Need to finalize MDOD schema, for XML file. References
b) Want to extend MDOD to cover all types of objects, i.e., software images. (NetKarma)
c) Want to use MDOD schema to define Event Record schema. (NetKarma)
d) MDOD registry. Use UNIS lookup service? Use DOR registry? Include in iRODS? Consider IF-MAP server?
e) MDOD creation and editing service.
f) Need object (e.g., Measurement Data Object or I&M Service) names; need a public reference; consider DataCite
g) Do we need object registry, with names and public key?

2) Who: Jason Zurawski (Internet2); Ezra Kissel (U Delaware); Eric Boyd (Internet2); Beth Plale (IU); Chris Small (GEMINI, IU); Scott Jensen (Indiana U); Larry Lannom (CNRI); LEAD Giridhar Manepalli (CNRI); Deniz Gurken (GIMI, UH); Harry Mussman (GPO)

4.6) Messaging Service

XML Messaging Service

Work in Progress

1) Definition of topic:

a) Use for messages, not generalized data; assume relatively low rate.
b) Use for OMF messages.
c) Use for "event record messages", that can be logged.
d) XMPP server, in public IP space.
e) Entities connect, and are authenticated.
f) An entity may start a pub/sub node.
g) When an entity subscribes, a message is sent to publisher requesting authorization.
h) Operations plan for XML Messaging Service.

2) Who: Rudra Dutta (NCSU); LEAD Anirban Mandal (RENCI); Christoph Dwertmann (NICTA); Ahmed El-Hassany (IU); Harry Mussman (GPO)

4.7) Lookup Service

Lookup Service

Work in Progress

1) Definition of topic:

a) Home and global Lookup Service, as defined by perfSONAR
b) Also Topology Service? c) Global UNIS? Also Local UNIS in slice?
d) Map MDOD into metadata that is registered
e) Can Lookup Service be used for finding web interfaces, and other types of portals?
f) Operations plan for Global UNIS.

2) Who: ? (GEMINI); Giridhar Manepalli (CNRI); Harry Mussman (GPO)

4.8) GENI User Workspace Service

Portal Service

Work in Progress

1) Definition of topic:

a) Towards Max Ott's vision that provides a unified environment for experiment support
b) GENI User Workspace Service is a container for a wide range tools including: experiment control tools; portal tools; measurement analysis and presentation tools
c) Is a Linux OS environment with files system, certificate and credential stores
d) Linux environment can be hosted on server dedicated to user; shared among multiple users in an organization; shared among multiple GENI users.
e) Many tools interact with GENI aggregates using GENI APIs
f) Many tools have a user interface, i.e.,a web interface; these are foten called portal tools
g) Many tools call other tools through published APIs.
h) Having all tools in the same container with a certificate store minimizes effort to gain authorizations.
i) Would prefer a service useful with both GIMI and GEMINI tools
j) Should compare with CNRI prototype User Workspace service
k) Operations plan for GENI User Worksapce service

2) Who: Jim Griffioen and/or Charles Carpenter (U Kentucky); Max Ott (NICTA); Christoph Dwertmann (NICTA); Chris Small, for NetKarma (Internet2); Ahmed El-Hassany (IU); Jeanne Ohren (GPO)

4.9) Archive Service

User Workspace and Archive Services

Work in Progress

1) Definition of topic:

a) Consider CNRI prototype user workspace and archive service
b) Consider U Kentucky archive service
c) Use iRODS service?
d) How to move data to service: move file; move SQL DB; or?
e) How are partitions for different users managed?
f) How is data in MDOD used to set archive sharing policy? what is required in MDOD?
g) Operations plan for Archive Service.

2) Who: Giridhar Manepalli (CNRI); LEAD Shu Huang (RENCI) ; Larry Lannom (CNRI); Wesley Wu (U Kentucky); Hussam Nasir (U Kentucky); Chris Small (NetKarma, IU)

4.10 List of Operational Services

Persistent Operational Services
Services Shared by GIMI and GEMINI

Work in Progress

1) What persistent operational services must be supported:

a) Descriptor registry. use UNIS? DOR? iRODS? IF-MAP?
b) Object registry. DOR?
c) XML messaging service
d) UNIS service
e) GENI user workspace service
f) iRODs archive service

2) Can all services can be shared by GIMI and GEMINI tools?

3) How do these relate to other GENI services/functions, including clearinghouse?

4) Who: Mike Zink (UMass Amherst); Martin Swany (Inidana U); Jim Griffioen (U Kentucky); Giridhar Manepalli (CNRI); Aaron Helsinger (GPO); Harry Mussman (GPO)