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

In addition, the GENI operations staff require extensive and reliable instrumentation and measurement capabilities to monitor and troubleshoot the GENI suite and its constituent entities. Some of this data will be made available to experimenters, to help them conduct useful and repeatable experiments.

The GMOC, providing GENI-wide operator services, needs to monitor essentially all GENI infrastructure on a 24x7 basis. In this case, the GMOC Operator will gather, analyze and present MD that monitors hundreds of infrastructure elements.

2) Tasks

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

T6) XML Messaging Service

In I&M, a Measurement Orchestration (MO) service needs to interact with the I&M services; one way to do so is to use the OMF interface, currently used (for example) by the OMF Experiment Controller to command an OMF Resource Controller (RC) that is installed next to an application.

The OMF messages are carried between an EC and RC by an XML pub/sub messaging service, based on an XMPP server.

For GENI, an XML Messaging service will be provided to carry these OMF messages, and thus enable orchestration.

However, such a service may have other useful functions, such as transporting Event Records (ERs).

To be generally useful, authentication and authorization functions must be provided.

For a detailed list of all goals defined for the XML Messaging service, see the Spiral 4 SOW of the IMF project.

T7) Measurement Information (MI) Service

A Lookup Service is a type of registry defined in the perfSONAR toolset; the availability of MD at perfSONAR interfaces MC services is registered there, using metadata describing the data and its location.

In addition, a similar Topology Service is used to store the topology of the network being examined.

Together, these services are combined in the Unified Network Information Service (UNIS).

The GEMINI project includes perfSONAR tools, and requires UNIS functions. Some will be provided locally (within the slice), but a global service is required if available MD is to be registered, so that users can find it and get it.

For GENI, the Measurement Information service (MI) will be provided to serve the need for a global UNIS service.

Can the MI service be used for other registry functions?

Can the MI service be used for finding web interfaces, and other types of portals?

Can the MI service be used to provide topology information to assist resource assignment and stitching in GENI?

2) Tasks

The MI service will be built by the GEMINI project using UNIS technology; see the Spiral 4 SOW of the GEMINI project for the detailed steps, which include:

T8) GENI User Services

Provide a way for a GENI user (e.g., experimenter or operator) to access a wide variety of "GENI User Services", where each user service provides an interface (e.g., API or GUI) to the user. Those user services with a GUI (web) interface are often called "portal services".

Together, the "GENI User Services" should provide all of the functions the user needs to setup and run their experiment, then gather, analyze and present the measurement data.

These services should work together via APIs, etc., to streamline the experiment process.

2) Tasks

Based upon the configuration defined below, the implementation is split into:

1) A GENI User Workspace, which is a persistent Linux OS environment dedicated to the user, that serves as a container for multiple user tools

2) Multiple GENI User Tools, where each provides a service with an interface or a "portal" to the user.

Define, prototype, deploy and operate a GENI User Workspace. It can be hosted on a server dedicated to the user, or on a server hosting multiple user workspaces for multiple users.

Gather the various "user tools" that have been implemented to date, and fit into GENI User Workspace Service so that GENI I&M users can begin to conveniently conduct experiments or instrument infrastructure.

Optimize "user tools" and their interfaces to better meet the needs of GENI users (e.g., experimenters and operators).

T9) Digital Object Archive (DOA) Service

Start with CNRI prototype digital object archive service
Plan transition to use of iRODS service
How to move data to service: move file; move SQL DB; or?
How is persistent object identifier (i.e., handle) generated? also registered? and later resolved? Include necessary Object Identifier (OI) service.
How are partitions for different users managed?
How is data in MDOD used to set archive sharing policy? what is required in MDOD?
Operations plans for Digital Object Archive (DOA) and Object Identifier (OI) services.