Difference between revisions of "VO Services Deployment and Configuration"

From Gcube Wiki
Jump to: navigation, search
Line 1: Line 1:
The 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. 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.
  
This User Interface offers to the VO Manager the possibility to select the ''Services'' and the target gHNs where the services will be deployed.
+
This User Interface offers to the VO Manager the possibility to select the Services and the target gHNs where they will be deployed.
''gHN''s that can be selected for deployment are those typed in bold in the Resource Browser panel, i.e., those made available by the local administrator according to institution policy or other reasons. Instead, the to-be-deployed ''Services'' the ones registered within the VO.
+
The gHNs that can be selected for deployment are those typed in bold in the Resource Browser panel, i.e., those made available by the local administrator according to institution policy or other reasons. Instead, the to-be-deployed ''Services'' the ones registered within the VO.
  
 
The selection/deselection of one ''GHN'' or ''Service'' can be done using the button on the header of Profile Visualizer panel.
 
The selection/deselection of one ''GHN'' or ''Service'' can be done using the button on the header of Profile Visualizer panel.

Revision as of 17:01, 6 October 2009

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.

This User Interface offers to the VO Manager the possibility to select the Services and the target gHNs where they will be deployed. The gHNs that can be selected for deployment are those typed in bold in the Resource Browser panel, i.e., those made available by the local administrator according to institution policy or other reasons. Instead, the to-be-deployed Services the ones registered within the VO.

The selection/deselection of one GHN or Service can be done using the button on the header of Profile Visualizer panel. When a GHN or a Service is selected, it is inserted into the "Selected Resource Tree". This tree can be browsed as the "Available Resource Tree". This allows the user to have a sort of basket to check the selected resources in each moment. For each selected GHN an additional entry is presented on the Resource Visualizer panel. In particular it is presented as Running Instances On <Name of Selected GHN> entry. Clicking on it, the Resource Browser panel lists the already available Running Instances on that GHN. This allows the administrator to evaluate a GHN. For example, the administrator can decide if the selected GHN is the proper one to host new Service[s] deployment.

When at least one GHN and one Service are selected a Deploy button appears on the left panel.

ServicesDeployment.png

Clicking on it the deploy process starts after a confirmation request has been fulfilled.

During the deployment the status is presented in the profile visualizer panel. The status is refreshed until the process is completed with a failure or with a success.

ServicesDeployment-01.png