Difference between revisions of "Administrator's Guide: How to set up a gCube infrastructure"

From Gcube Wiki
Jump to: navigation, search
(→‎Minimal configuration)
(→‎Other possible configurations)
 
(106 intermediate revisions by 7 users not shown)
Line 1: Line 1:
−
A ''gCube infrastructure'' is a set of working nodes (so-called DHNs, DILIGENT Hosting Nodes) glued by the gCube enabling services and able to host gCube services in a cooperative way. When creating a new infrastructure, there are two kinds of configuration: secure configuration and non-secure configuration The setup of the latter is easier than the former, since the secure infrastructures require some additional steps.<br>
+
[[Category:Administrator's Guide]]
−
== Non-secure configuration ==
+
__NOTOC__
−
==== Minimal configuration ====
+
{| align="right" style="color:red; border:1px solid #aaa; background-color: #f9f9f9; padding: 5px; font-size: 95%;" cellspacing="0"
−
The setup a minimal configuration of a non-secure infrastructure requires the following steps:
+
|+  <b>Section contents</b>
 +
|-
 +
|[[Administrator's_Guide:How_to_set_up_a_gCube_infrastructure#Minimal_deployment_scenario|1 Minimal deployment scenario]]
 +
|-
 +
|[[Administrator's_Guide:How_to_set_up_a_gCube_infrastructure#Other_possible_configurations|2 Other possible configurations]]
 +
|}
 +
A ''gCube infrastructure'' is a set of working nodes (so-called gHNs, gCube Hosting Nodes) glued by the gCube enabling services and able to host gCube services in a cooperative way.
 +
<br>
  
−
#decide the VOs hierarchy configuration: at least one root VO and a subVO are required to be there
+
=== Minimal deployment scenario ===
−
#identify a set of machines to turn on as DHNs (their number may vary depending on the infrastructure needs)
+
−
#prepare a VO Map XML file for each VO
+
−
#setup the root VO
+
−
##identify two machines to dedicate to the VO management
+
−
##[[DHN_Installation|install the DHN 1.0 bundle]] in the two machines and copy the VO Map files under the ''$GLOBUS_LOCATION/etc/org_diligentproject_keeperservice_hnm/VOMaps'' folder
+
−
##[[DHN_Installation#Post-installation_configuration|configure]] one DHN (named ''DIS root DHN'') as root, join it to the root VO as default VO and [[Core_Services_Installation#DILIGENT_Information_Service_.28DIS.29|install the DIS core services]] (DIS-IC, DIS-Registry, DIS-Broker) there dedicated to the management of the root VO
+
−
##[[DHN_Installation#Post-installation_configuration|configure]] one DHN (named ''DLMan root DHN'') to join it to the root VO as default VO and
+
−
##*[[Core_Services_Installation#Package_Repository|install and populate a Package Repository]] there
+
−
##*[[Core_Services_Installation#DL_Management|install and configure a DL Management Service]] there
+
−
##start the container on the ''DIS root DHN'' and then on the ''DLMan root DHN'' and verify that they work properly
+
−
#setup the subVO
+
−
##identify two machines to dedicate to the subVO management
+
−
##[[DHN_Installation|install the DHN 1.0 bundle]] in the two machines and copy the VO Map files under the ''$GLOBUS_LOCATION/etc/org_diligentproject_keeperservice_hnm/VOMaps'' folder
+
−
##[[DHN_Installation#Post-installation_configuration|configure]] one DHN as root, join it to the subVO as default VO and [[Core_Services_Installation#DILIGENT_Information_Service_.28DIS.29|install the DIS core services]] (DIS-IC, DIS-Registry, DIS-Broker) there dedicated to the subVO (named ''DIS subVO DHN'')
+
−
##[[DHN_Installation#Post-installation_configuration|configure]] one DHN (named ''DLMan subVO DHN'') to join it to the subVO as default VO and [[Core_Services_Installation#DL_Management|install and configure a DL Management Service]] there
+
−
##start the container on the ''DIS subVO DHN'' and then on the ''DLMan subVO DHN'' and verify that they work properly
+
−
#configure and start generic DHNs
+
−
##[[DHN_Installation|install the DHN 1.0 bundle]] in each machine and copy the VO Map files under the ''$GLOBUS_LOCATION/etc/org_diligentproject_keeperservice_hnm/VOMaps'' folder
+
−
##[[DHN_Installation#Post-installation_configuration|configure]] the DHNs to join the subVO as default VO:
+
−
##start the container on each machine and verify that the DHN is correctly published both in the root VO and in the subVO DIS
+
−
#setup the portal by following the [[DILIGENT Gridsphere and Portal Security patch]] instructions.
+
−
#configure one or more VREs by exploiting the [[Administration]] user interface capability reported in the User's Guide manual.
+
  
−
==== Other possible configurations ====
+
In this section, we report the steps to setup a gCube infrastructure:
−
== Secure configuration ==
+
−
==== Minimal configuration ====
+
  
−
==== Other possible configurations ====
+
#decide the [https://gcore.wiki.gcube-system.org/gCube/index.php/Scope_Management#Modelling_Scope scope] configuration, i.e. the name of the infrastructure
−
<br>
+
#identify a set of machines to turn on as gHNs (their number may vary depending on the Infrastructure needs)
−
<br>
+
#[[Information_System_Installation#Service_Map|prepare a Service Map]] file for the infrastructure
−
[[User:Manuelesimi|Manuelesimi]] 19:59, 4 December 2007 (EET)
+
#install the infrastructure enabling services:
 +
##identify 3 machines to dedicate to the Infrastructure Enabling Services
 +
##[https://gcore.wiki.gcube-system.org/gCube/index.php/Administrator_Guide#Installation install gCore] in the 3 machines and copy the two Service Map files under the ''$GLOBUS_LOCATION/config'' folder
 +
##[https://gcore.wiki.gcube-system.org/gCube/index.php/Administrator_Guide#Configuration configure] the first gHN to join to the infrastructure scope and
 +
##* deploy and configure an [[Information_System_Installation#Version_2.0.0_or_higher|IS-Collector]] instance and configure it to join the infrastructure scope
 +
##[https://gcore.wiki.gcube-system.org/gCube/index.php/Administrator_Guide#Configuration configure] the second gHN as ROOT and to join to the infrastructure scope and
 +
##* deploy and configure an [[Information_System_Installation#IS-Registry|IS-Registry]] instance and configure it to join the infrastructure scope
 +
##* deploy and configure an [[Information_System_Installation#IS-Notifier|IS-Notifier]] instance and configure it to join the infrastructure scope
 +
##[https://gcore.wiki.gcube-system.org/gCube/index.php/Administrator_Guide#Configuration configure] the third gHN to join it to the infrastructure scope and
 +
##* deploy a [[VRE_Management_Installation#Software_Gateway|Software Gateway]] instance and configure it to join both the infrastructure and the VO scope
 +
##* deploy a [[VRE_Management_Installation#Resource_Manager|Resource Manager]] instance and a [[VRE_Management_Installation#Resource_Broker|Resource Broker]] instance and configure them to join the infrastructure scope
 +
##start the 3 containers following the order of the deployments and verify that they work properly
 +
 
 +
=== Other possible configurations ===
 +
Alternative configurations can improve the infrastructure performances. In particular:
 +
* the IS-Notifier can be hosted on a different gHN with respect to the IS-Registry service
 +
* the Software Gateway can be hosted on a different gHN with respect to the Resource Management services
 +
* multiple Virtual Organizations can be defined and deployed
 +
 
 +
The 'optimal' configuration mainly depends on the number of available gHNs and on the expected exploitation of the infrastructure. The more gHNs join the infrastructure the better distribution of resources and services across them is doable.

Latest revision as of 10:16, 10 April 2015


Section contents
1 Minimal deployment scenario
2 Other possible configurations

A gCube infrastructure is a set of working nodes (so-called gHNs, gCube Hosting Nodes) glued by the gCube enabling services and able to host gCube services in a cooperative way.

Minimal deployment scenario

In this section, we report the steps to setup a gCube infrastructure:

  1. decide the scope configuration, i.e. the name of the infrastructure
  2. identify a set of machines to turn on as gHNs (their number may vary depending on the Infrastructure needs)
  3. prepare a Service Map file for the infrastructure
  4. install the infrastructure enabling services:
    1. identify 3 machines to dedicate to the Infrastructure Enabling Services
    2. install gCore in the 3 machines and copy the two Service Map files under the $GLOBUS_LOCATION/config folder
    3. configure the first gHN to join to the infrastructure scope and
      • deploy and configure an IS-Collector instance and configure it to join the infrastructure scope
    4. configure the second gHN as ROOT and to join to the infrastructure scope and
      • deploy and configure an IS-Registry instance and configure it to join the infrastructure scope
      • deploy and configure an IS-Notifier instance and configure it to join the infrastructure scope
    5. configure the third gHN to join it to the infrastructure scope and
    6. start the 3 containers following the order of the deployments and verify that they work properly

Other possible configurations

Alternative configurations can improve the infrastructure performances. In particular:

  • the IS-Notifier can be hosted on a different gHN with respect to the IS-Registry service
  • the Software Gateway can be hosted on a different gHN with respect to the Resource Management services
  • multiple Virtual Organizations can be defined and deployed

The 'optimal' configuration mainly depends on the number of available gHNs and on the expected exploitation of the infrastructure. The more gHNs join the infrastructure the better distribution of resources and services across them is doable.

Retrieved from "https://gcube.wiki.gcube-system.org/index.php?title=Administrator%27s_Guide:_How_to_set_up_a_gCube_infrastructure&oldid=22296"