Difference between revisions of "VRE Manager"

Revision as of 17:06, 25 September 2008

The VRE Manager is a gCube Service grouping the facilities for managing the constituents of the VREs, namely the service instances. It is the service in charge to coordinate the overall deployment and operation of each VRE. Moreover, it takes care to interact with the Virtual Organisation Management to create the VO needed to support the operation of the VREs.

Architecture

Within the gCube architecture, the VREManage is placed at the top of a stack of the VREManagement services, below only the VREModeler. From a implementation point of view, the VREManager adopts the Singleton pattern. In particular, it creates and manages a resource maintaing the management information of the resources belonging the Scope.

Functions

The main functions supported by VREManagerFactory are:

• createVO() – which takes as input parameter a message containing a VO name, a Description, a Boolean value indicating whether the Virtual Organisation is requested to operate in a fully-fledged security context or not, the ID of the manager (i.e. the actor to be informed on the activities of this VO), the list of the Running Instances and gHNs that have to join the VO and returns the reference to the Resource that represents the so specified VO;
• createVRE() – which takes as input parameter a message containing a VRE ID, a VRE name, a Description, the ID of the designer and manager (i.e. the actor to be informed on the activities of this VRE), the URL of the resulting portal, the VRE specification (i.e. Collection, Service, Running Instances, gHNs and other constituents that have to be part of the VRE) and returns the reference to the Resource that represents the so specified VRE;

The main functions supported by VREManagerVOScopeService are:

• DeployVO() – which starts and coordinates the deployment actions needed to implement the given VO;
• DeployService() – which takes as input parameter a message containing Service ID and, optionally, the gHN ID and deploys it in the current VO. If the gHN is not specified the VRE Manager interacts with the Broker and Matchmaker to identify a suitable gHN;
• DeploySecureService() – which takes as input parameter a message containing Service ID and, optionally, the gHN ID and deploys it in the current VO by appropriately creating the security context for the operation of the resulting Running Instance. If the gHN is not specified the VRE Manager interacts with the Broker and Matchmaker to identify a suitable gHN;
• UndeployService() – which takes as input parameter a message containing the gHN ID and the Service ID and perform the un-deployment of the given service from the selected hosting node. This operations is accomplished by interacting with the gHN Manager;
• CheckDeployStatus() – which returns a message exposing the status of the deployment activity in the VO. In particular, the list of the currently deployed Software Archives and Packages as well as the number of re-deployment actions performed are reported;
• CheckVOStatus() – which returns a message exposing the current operational status of the VO in terms of the status of its constituents. In particular, this message contains the list of Running Instances currently active;
• removeVO() – which dismiss the VO it is invoked on. In particular, it un-deploys all the running instances serving that VO as well as all the VRE and the relative constituents running in the context of the selected VO;

The main functions supported by VREManagerVREScopeService are:

• updateVRE() – which takes as input parameter a message containing an updated version of the VRE specification including the list of the gHNs, the list of Services and Running Instance, the list of Collections and revises the existing VRE accordingly, e.g. by deploying new Running Instances or undeploying existing Running Instances;
• DeployService() – which takes as input parameter a message containing Service ID and, optionally, the gHN ID and deploys it in the current VRE. If the gHN is not specified the VRE Manager interacts with the Broker and Matchmaker to identify a suitable gHN;
• DeploySecureService() – which takes as input parameter a message containing Service ID and, optionally, the gHN ID and deploys it in the current VRE by appropriately creating the security context for the operation of the resulting Running Instance. If the gHN is not specified the VRE Manager interacts with the Broker and Matchmaker to identify a suitable gHN;
• UndeployService() – which takes as input parameter a message containing the gHN ID and the Service ID and perform the un-deployment of the given service from the selected hosting node. This operations is accomplished by interacting with the gHN Manager;
• CheckDeployStatus() – which returns a message exposing the status of the deployment activity in the VRE. In particular, the list of the currently deployed Software Archives and Packages as well as the number of re-deployment actions performed are reported;
• CheckVREStatus() – which returns a message exposing the current operational status of the VRE in terms of the status of its constituents. In particular, this message contains the list of Running Instances currently active;
• removeVRE() – which dismiss the VRE it is invoked on. In particular, it un-deploys all the running instances serving the VRE in exclusive manner while manages appropriately the Running Instances that serve diverse VREs.