wiki:InstMeasCurrentDesignTopicsAll

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

--

4) GENI I&M Priority Design Topics

Description

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.

Goals

Resolve between now (GEC12) and GEC13.

Simplify where possible!

Approach

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

List:

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

1) Definition of topic:

a) How do we work towards Max Ott's vision for experiment support? slides

b) Nominal experiment use case:

1) Setup and run experiment using Experiment Control Tools, Experiment Orchestration Service and Lab Portal.
2) Setup and run measurements using services within slice, and persistent services. Option: get measurement data from persistent MP.
3) Gather MD, and observe during experiment; formulate MDOD.
4) Archive MD with MDOD.
5) Share archived MD with others, per policy included within MDOD.
6) Pull MD out of archive, to analyze and/or visualize.

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

2) Who: Max Ott (NICTA); Jim Griffioen (U Kentucky); Prasad Calyam (Ohio Super Center); Mike Zink (UMass Amherst)

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

I&M Use Cases for Infrastructure Measurement
Support for Operators

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: Martin Swany (Indiana U); Eric Boyd (Internet2); Jason Zurawski (Internet2); Chris Small (Indiana U); Ilia Baldine, for ExoGENI racks (RENCI); ?, for InstaGENI racks (?)

4.4) GENI Environment

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

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:

1) FLACK
2) GUSH (with Omni)
3) SFACE + RAVEN

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); Tom Mitchell (GPO); Aaron Helsinger (GPO)

4.5) Descriptors, Objects and Registries, and Lookup Service

Descriptor Schema and Registry Service
Object Names and Registry Service
Lookup Service

1) Definition of topic:

a) MDOD schema, for XML file. References

b) MDOD registry. Use DOR registry? Include in iRODS? Consider IF-MAP server?

c) Object (e.g., I&M service) names.

d) Object registry, with names and public key.

e) Home and global Lookup Service, as defined by perfSONAR

f) Map MDOD into metadata that is registered

g) Can Lookup Service be used for finding portals?

h) Also Topology Service? following UNIS?

2) Who: Jason Zurawski (Internet2); Ezra Kissel (U Delaware); Eric Boyd (Internet2); Scott Jensen (Indiana U); Larry Lannom (CNRI); LEAD Giridhar Manepalli (CNRI); Deniz Gurken (UH); Aaron Helsinger (GPO)

4.6) Messaging Service

XML Messaging Service

1) Definition of topic:

a) XMPP server, in public IP space. Consider AMQP server? Consider IF-MAP server?

b) Entities connect, and are authenticated.

c) An entity may start a pub/sub node.

d) When an entity subscribes, a message is sent to publisher requesting authorization.

e) Use for OMF messages.

f) Use for "event record messages".

2) Who: Rudra Dutta (NCSU); Shu Huang (RENCI); Chirstoph Dwertmann (NICTA); Martin Swany (IU); Prasad Calyam (OSC); Deniz Gurken (UH)

4.7) Lookup Service

Lookup Service

Note: Merged into 4.5)

4.8) Portal Service

Portal Service

1) Definition of topic:

a) Towards Max Ott's vision for experiment support

b) Consider INSTOOLS portal service

c) Define portal service for GIMI tools, with multiple functions.

d) How are partitions for different users managed?

e) Can these portal services be merged?

f) Are these portal services really a combination of gateway and user workspace services?

2) Who: Jim Griffioen or ? (U Kentucky); Christoph Dwertmann (NICTA); Jason Zurawski, for NetKarma (Internet2)

4.9) User Workspace and Archive Services

User Workspace and Archive Services

1) Definition of topic:

a) Consider CNRI prototype user workspace and archive service

b) Consider U Kentucky archive service

c) Consider 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?

2) Who: Giridhar Manepalli (CNRI); Shu Huang (RENCI) ; Larry Lannom (CNRI); Wesley Wu (U Kentucky)

4.10 Operational Services

Persistent Operational Services
Services Shared by GIMI and GEMINI

1) Definition of topic:

a) What persistent operational services must be supported:

1) Descriptor registry. DOR? iRODS? IF-MAP?
2) Object registry. DOR?
3) XML messaging service
4) Home and global Lookup Services; also Topology Service? UNIS?
5) INSTOOLS portal service
6) GIMI portal service
7) U Kentucky archive service
8) CNRI prototype user workspace and archive service
9) iRODs archive service

b) What services can be shared by GIMI and GEMINI tools?

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

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