Difference between revisions of "GCube Infrastructure Enabling Services"

Revision as of 00:51, 2 August 2011

The gCube Infrastructure Enabling Services collectively form the lower layer of the gCube framework whose role is to glue together and support the overall operation and management of the rest of constituents of a gCube based e-Infrastructure. The following classes of facilities are offered by the enabling services to the rest of the gCube infrastructure actors:

→ resources publishing and discovery

→ resources controlled sharing support

→ resources deployment and orchestration

→ resources selection support

→ and resource workflows definition and operation.

These facilities are globally delivered by a set of services, software libraries and related technologies described in the following.

Overall Architecture

The gCube Infrastructure Enabling Services consist of three cooperating subsystems whose role, functions and relations are the following:

• The Information System represents the “core” of the infrastructure playing the role of a Registry in a gCube based Infrastructure. All actors partaking to a gCube based infrastructure are expected to interact with it in order to

(i) inform the rest of the resources about its presence and its distinguishing features;

(ii) discover the resources they are interested to interact with in order to accomplish its functionality.

Two client libraries, the IS-Publisher (production/publishing) and the IS-Client (discovery/consumption), are distributed as part of this subsystem to facilitate such interactions and to decouple the producer and consumer service logic from the internal organization and deployment of the IS services. This decoupling is fundamental because the IS services can be replicated and distributed across multiple VOs depending on

• the high workload they could be subject to,
• the robustness and fault-resiliency expected by such a critical component,
• new service IS instances are dynamically deloyed

This way such dynamicity is completely transparent to the Information System clients.

• The Virtual Organisation Management represents the subsystem securing the sharing and reuse of the constituents a gCube based Infrastructure, i.e. all the managed resources. The subsystem implements a security framework realizing the Virtual Organization model on which the GCube Security Model is based. The main functions of this subsystem are related to authentication and authorization. Because of this role, some of the components of this subsystem are expected to be ubiquitous in a gCube-based infrastructure as to facilitate the exploitation of these features. VO Management is also in charge to provide mechanisms to achieve a production level interoperability with identified external infrastructures.

• The VRE Management is in charge for the definition and deployment of such Virtual Research Environments (VREs) by exploiting the resources of a gCube based Infrastructure. Thus, it needs to interact with the Information System to be acquainted of the resources that are available as well as of their status, to select them appropriately and finally to monitor the VRE operations. Moreover, it is requested to interact with the Virtual Organisation Management to both act securely and create the security context supporting each Virtual Research Environment. The main achievement is the deployment phase where the optimal pool of resources is identified and deployed in order to create a VRE compliant with its definition. From an architectural point of view it is characterised by (i) services implementing the front-end (VRE Modeler) mediating between the users' high level requirements and the subsystem back-end; (ii) services coordinating the deployment and operation of the VRE (Resource Manager); and Services supporting the dynamic deployment (Deployer, Software Repository and gHN Manager).