Difference between revisions of "VRE Management"

Revision as of 22:25, 24 July 2008

VRE Management

The VRE Management subsystem is the family of services and software components responsible for: (i) the definition of VREs and (ii) the dynamic deployment of VREs and their resources across the infrastructure. The VREs definitions are declaratively specified through an appropriate and user-friendly user interface in a dedicated language. Through the same interface the designer is informed on the optimal deployment plan identified by the system. The plan is based on availability, QoS requirements, resource inter-dependencies, and VRE sharing policies, but also on monitoring of failures (resources are dynamically redeployed) and load (resources are dynamically replicated). Three distinguished services (Software Repository, Broker and Matchmaker, gCube Hosting Node Manager), under the coordination of the VRE Manager, support VRE dynamic deployment by, respectively, collecting service implementations, selecting target nodes for deployment within the infrastructure, and hosting resources implementations at selected nodes.

Reference Architecture

This subsystem supports the implementation of Virtual Research Environments from their definition/specification to their operation and maintenance. The services forming the subsystem have been organised as depicted in Figure 1 and described below.

To implement its role the VRE Management subsystem is organized in the following main services:

• VRE Modeler – this Service enables users/communities (VRE Designers) to define VREs and VRE Administrators to actually create them and monitor their operational status. It allows the definition of a set of criteria by specifying the expected characteristics of the new VRE; starting from them, it identifies the set of resources required to provide the requested features. Both the characterization criteria and the resulting set of resources constitute the VRE Definition document;
• VREManagerVRE Manager – this Service coordinates the activities needed to transform a VRE as specified in a VRE Definition document into a running set of coordinated and cooperating resources implementing it. Because of its central role, it is requested to operate with almost all services forming the VRE management subsystem as well as with the rest of the services forming the backbone of a gCube based infrastructure, i.e. the Information System, the Virtual Organisation Management Service, the Broker and Matchmaker and the Process Management. In particular, it creates and makes publicly available through the IS the VRE Profile, i.e. the operational context needed to properly operate the pool of resources forming the VRE;
• GHN Manager – this Service is deployed on each of gCube nodes as one of the local services contributing to form the gHN. It provides the VRE Manager service with an entry point for managing the node, e.g. installing the mandatory software, publishing node information;
• Deployer – this Service is another example of local service equipping any gHN in order to provide the VRE Manager with the facilities needed to deploy, manage and un-deploy software components on it. Through this feature, the VRE Manager can dynamically relocate the constituents of any VRE as to implement policies aiming at maximising the usage of existing assets;
• Software Repository – this Service is in charge of providing a gCube based infrastructure with the software components needed to operate Virtual Research Environments. In particular, it stores the software bundles that once deployed on a gHN originates a new resource (Running Instance) that can be used in the context of one or more VREs;