Difference between revisions of "VO Services Deployment and Configuration"

From Gcube Wiki
Jump to: navigation, search
m
 
(39 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
[[Category:Administrator's Guide]]
 +
__NOTOC__
 +
 +
=== VO Services  ===
 +
Besides the Enabling Services, in a typical deployment scenario, a subset of the gCube Services are deployed at VO level (while the remaining part is deployed at VRE level). The criteria for selecting the target scope level for a specific service are:
 +
* better performances in case of shared instances
 +
* complexity of the service's initialization/state creation
 +
* special requirements on the target gHN (such as a local DBMS instance)
 +
* high demand of storage/computational resources
 +
 +
The recommended deployment scenario, it is suggested to deploy at VO level the following groups of services:
 +
* Content Management
 +
* Index Management
 +
* Personalisation Services
 +
* VRE Modeler
 +
 +
Then, according to the VO needs, other services could be optionally deployed at VO level:
 +
* Time Series
 +
* Ontology Management
 +
* Data Transformation Services
 +
 +
=== Preparing the hosting gHNs  ===
 +
 +
Before to proceed with the services' deployment, the related hosting gHNs must be prepared in order to host their running instances. In the suggested deployment scenario, at least 5 machines must be turned as gHNs.
 +
 +
Per each machine:
 +
#[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Installation install gCore] and copy the Service Map files under the ''$GLOBUS_LOCATION/config'' folder
 +
#[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] the gHN to join the VO scope
 +
#[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Verify_the_Installation start the container] and verify that the gHN is correctly published both in the infrastructure and in the VO Information Systems.
 +
 +
These 5 gHNs will be used to host the 5 suggested groups of services enumerated in the previous section.
  
 
=== Dynamic Deployment in gCube  ===
 
=== Dynamic Deployment in gCube  ===
  
−
''Dynamic Deployment'' is a key feature of the gCube system. With this term we refer the final step of a process that starts with the description of the components provided by developers and ends with the possibility to remotely deploy any service of the gCube system.  
+
''Dynamic Deployment'' is a key feature of the gCube system. It refers to the possibility to remotely deploy any service of the gCube system on any gHNs available in a Scope.
 +
An authorized user (VO-Manager) can perform deployment on a VO with the features offered by the [https://gcube.wiki.gcube-system.org/gcube/index.php/Resource_Management Resource Management Portlet].
  
−
In this part of the section the User Interface allowing the VO Manager to access to the dynamic deployment features is presented.
+
Dynamic Deployment is the default way to deploy the VO-level Services presented below.
  
−
The interface is divided in three main panels:
+
=== VRE Modeler ===
−
* on the left area (named '''Service Deployment''' panel), the '''Available Resource'''  menu allows to select the to-be-deployed ''Services'' and the target ''gHNs'' (i.e. where they will be deployed). The available gHNs are the ones belonging the VO, while the available Services are the ones registered within the VO;
+
−
* when gHN or Service is selected, the list of available resources is displayed in the upper right area named '''Resource Browser''' panel,
+
−
* finally, when a resource is selected, its profile is displayed in the lower right area named '''Resource Profile''' panel.
+
  
−
The selection/deselection of a gHN and/or Service can be done using the related button on the header of Profile Visualizer panel. When a gHN or a Service is selected, it is inserted into the '''"Selected Resource"''' tree in the lower part of the left side panel. This tree can be browsed and this allows the user to have a sort of basket to check the selected resources in each moment. Moreover, deselections can be done on its content any time before to request the deployment.
+
The following service has to be selected for dynamic deployment:
  
−
Once a gHN is selected, an additional entry is presented in the Service Deployment named '''Running Instances On <Name of Selected GHN>'''. By clicking on it, the Resource Browser panel lists the already available ''Running Instances'' hosted on that gHN. This allows the VO Manager to evaluate a gHN and understand if this is the correct target node.
+
* VRE Modeler
  
−
[[Image:ServicesDeployment-02.png]]
+
It does not have any requirement on the target gHN.
  
−
At least one gHN'' and one Service have to be selected. Afterwards, a '''Deploy''' button appears on the left panel. By clicking on it, the deployment starts (after a confirmation request).
+
=== Data Transformation ===
  
−
During the deployment, the state of the deployment activity is presented in the Resource Profile panel. The state is refreshed until the process is completed.
+
The following service has to be selected for dynamic deployment:
  
−
[[Image:ServicesDeployment-01.png]]
+
* DataTransformationService
  
−
In the following, we will present how to deploy the VO level services.
+
It does not have any requirement on the target gHN.
  
 +
=== Index Management ===
  
−
=== Index Management ===
+
The following services have to be selected:
 +
* Index Lookup
 +
* Index Management
 +
* Index Updater
  
 +
These services are both memory and storage demanding, therefore the target dedicated gHN must match these characteristics (their values mainly depend on the VO expected content).
  
−
=== Metadata Management ===
+
=== Ontology Management ===
  
 +
The following service has to be selected:
 +
 +
* OntologyManagementService
 +
 +
It does not have any special requirement on the target gHN.
  
 
=== Content Management ===
 
=== Content Management ===
 +
 +
The following services have to be selected for dynamic deployment:
 +
 +
* Content Manager
 +
* View manager
 +
* Storage Management
 +
* Archive Import
 +
 +
and installed on a clean gHN with a storage capacity of > 50 GB (this value mainly depends on the VO expected content).
 +
 +
Optionally, depending on the VO needs, the following service is selected and installed on a separated gHN:
 +
 +
* TimeSeriesService
 +
 +
This service requires an instance of MySQL DBMS on the target node.
 +
 +
=== gCube Personalization ===
 +
 +
The following services have to be selected for dynamic deployment:
 +
 +
* User Profile Access
 +
 +
 +
They do not have any special requirement on the target node.

Latest revision as of 09:09, 24 July 2013


VO Services

Besides the Enabling Services, in a typical deployment scenario, a subset of the gCube Services are deployed at VO level (while the remaining part is deployed at VRE level). The criteria for selecting the target scope level for a specific service are:

  • better performances in case of shared instances
  • complexity of the service's initialization/state creation
  • special requirements on the target gHN (such as a local DBMS instance)
  • high demand of storage/computational resources

The recommended deployment scenario, it is suggested to deploy at VO level the following groups of services:

  • Content Management
  • Index Management
  • Personalisation Services
  • VRE Modeler

Then, according to the VO needs, other services could be optionally deployed at VO level:

  • Time Series
  • Ontology Management
  • Data Transformation Services

Preparing the hosting gHNs

Before to proceed with the services' deployment, the related hosting gHNs must be prepared in order to host their running instances. In the suggested deployment scenario, at least 5 machines must be turned as gHNs.

Per each machine:

  1. install gCore and copy the Service Map files under the $GLOBUS_LOCATION/config folder
  2. configure the gHN to join the VO scope
  3. start the container and verify that the gHN is correctly published both in the infrastructure and in the VO Information Systems.

These 5 gHNs will be used to host the 5 suggested groups of services enumerated in the previous section.

Dynamic Deployment in gCube

Dynamic Deployment is a key feature of the gCube system. It refers to the possibility to remotely deploy any service of the gCube system on any gHNs available in a Scope. An authorized user (VO-Manager) can perform deployment on a VO with the features offered by the Resource Management Portlet.

Dynamic Deployment is the default way to deploy the VO-level Services presented below.

VRE Modeler

The following service has to be selected for dynamic deployment:

  • VRE Modeler

It does not have any requirement on the target gHN.

Data Transformation

The following service has to be selected for dynamic deployment:

  • DataTransformationService

It does not have any requirement on the target gHN.

Index Management

The following services have to be selected:

  • Index Lookup
  • Index Management
  • Index Updater

These services are both memory and storage demanding, therefore the target dedicated gHN must match these characteristics (their values mainly depend on the VO expected content).

Ontology Management

The following service has to be selected:

  • OntologyManagementService

It does not have any special requirement on the target gHN.

Content Management

The following services have to be selected for dynamic deployment:

  • Content Manager
  • View manager
  • Storage Management
  • Archive Import

and installed on a clean gHN with a storage capacity of > 50 GB (this value mainly depends on the VO expected content).

Optionally, depending on the VO needs, the following service is selected and installed on a separated gHN:

  • TimeSeriesService

This service requires an instance of MySQL DBMS on the target node.

gCube Personalization

The following services have to be selected for dynamic deployment:

  • User Profile Access


They do not have any special requirement on the target node.

Retrieved from "https://wiki.gcube-system.org/index.php?title=VO_Services_Deployment_and_Configuration&oldid=19362"