GCore Based Information System Specification

From Gcube Wiki
Revision as of 15:26, 27 February 2012 by Manuele.simi (Talk | contribs) (Philosophy)

Jump to: navigation, search

Overview

The Information System (IS) is the core subsystem connecting producers of resources to their consumers. It acts as a registry of the infrastructure by offering global and partial views of its resources and their current status.

The approach provided by the IS is of great support for the dynamic deployment capabilities and the interoperability solutions offered by the Resource Management facilities.

Key features

Resource Publication, Access and Discovery
IS is the connecting point among the resources of the e-Infrastructure


Consistency with the new Resource Model
IS grants publication and access to resource compliant with the evolved Resource Model
Support to Standards - WS-DAIX Specification v1.0
IS offers a full implementation of WS-DAIX v.1.0, a widely accepted standard defining a set of data access interfaces for XML data resources
Support to Standards - XQuery 1.0
Resource discovery can be performed through expressions compliant with XQuery 1.0
Support to Standards - WS-Notifications
Consumers of resources can subscribe to the IS for receiving WS-Notifications about any change occurred in they resources the are interested in
Distribution
...
Responsiveness
each query served in milliseconds
Scalability
...
Reliableness
...

Design

Philosophy

The IS has been designed and implemented to:

  • rely on standards
  • support distribution at maximum and replication wherever it is possible
  • abstract clients from the deployment scenario

Resource Model

The core of the IS is the Resource Model defined in gCube. A second generation of the model is shaped and being integrated.

[TBP]

Architecture

To deliver the quality of service and performances and to handle growing amounts of information (scalability), the Information System is composed by a set of Web Services and client libraries.

Information System Architecture

Deployment

Usually, a subsystem consists of a number of number of components. This section describes the setting governing components deployment, e.g. the hardware components where software components are expected to be deployed. In particular, two deployment scenarios should be discussed, i.e. Large deployment and Small deployment if appropriate. If it not appropriate, one deployment diagram has to be produced.

Large deployment

A deployment diagram suggesting the deployment schema that maximizes scalability should be described here.

Small deployment

A deployment diagram suggesting the "minimal" deployment schema should be described here.

Use Cases

The subsystem has been conceived to support a number of use cases moreover it will be used to serve a number of scenarios. This area will collect these "success stories".

Well suited Use Cases

UC: Resource Publication

File:ResourceAllocation.png
UC: Resource Publication


UC: Resource Discovery

File:ResourceAllocation.png
UC: Resource Discovery


UC: Resource Access

File:ResourceAccess.png
UC: Resource Access


UC: Resource Notifications

File:ResourceNotifications.png
UC: Resource Notifications


UC: Mediator among Resource Models

File:ResourceMediation.png
UC: Resource Mediation


Less well suited Use Cases

Describe here scenarios where the subsystem partially satisfied the expectations.