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

From Gcube Wiki
Jump to: navigation, search
(→‎Minimal deployment scenario)
(→‎Other possible configurations)
 
(22 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
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. When creating a new infrastructure, there are two kinds of configuration: secure configuration and non-secure configuration.  
+
[[Category:Administrator's Guide]]
 +
__NOTOC__
 +
{| align="right" style="color:red; border:1px solid #aaa; background-color: #f9f9f9; padding: 5px; font-size: 95%;" cellspacing="0"
 +
|+  <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>
 
<br>
−
== Non-secure configuration ==
 
  
−
==== Minimal deployment scenario ====
+
=== Minimal deployment scenario ===
  
−
In this section, we report the steps to setup a gCube infrastructure with one Virtual Organization (VO):
+
In this section, we report the steps to setup a gCube infrastructure:
  
−
#decide the [https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Scope_Management#Modelling_Scope scope] hierarchy configuration, i.e. the names of the Infrastructure and of the VO
+
#decide the [https://gcore.wiki.gcube-system.org/gCube/index.php/Scope_Management#Modelling_Scope scope] configuration, i.e. the name of the infrastructure
−
#identify a set of machines to turn on as gHNs (their number may vary depending on the infrastructure needs)
+
#identify a set of machines to turn on as gHNs (their number may vary depending on the Infrastructure needs)
−
#[[Information_System_Installation#Service_Map|prepare a Service Map]] file for each scope (Infrastructure and VO)
+
#[[Information_System_Installation#Service_Map|prepare a Service Map]] file for the infrastructure
−
#setup the Infrastructure:
+
#install the infrastructure enabling services:
 
##identify 3 machines to dedicate to the Infrastructure Enabling Services
 
##identify 3 machines to dedicate to the Infrastructure Enabling Services
−
##[https://wiki.gcore.research-infrastructures.eu/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#Installation install gCore] in the 3 machines and copy the two 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 to the infrastructure scope and  
+
##[https://gcore.wiki.gcube-system.org/gCube/index.php/Administrator_Guide#Configuration configure] the first gHN to join to the infrastructure scope and  
−
##* deploy the [[Information_System_Installation#Version_2.0.0_or_higher|IS-Collector]] on the node
+
##* 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://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] the second gHN as ROOT and to join to the infrastructure scope and  
+
##[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 the [[Information_System_Installation#IS-Registry|IS-Registry]] on the node
+
##* deploy and configure an [[Information_System_Installation#IS-Registry|IS-Registry]] instance and configure it to join the infrastructure scope
−
##* deploy the [[Information_System_Installation#IS-Notifier|IS-Notifier]] on the node
+
##* deploy and configure an [[Information_System_Installation#IS-Notifier|IS-Notifier]] instance and configure it to join the infrastructure scope
−
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] one third gHN to join it to the infrastructure scope and
+
##[https://gcore.wiki.gcube-system.org/gCube/index.php/Administrator_Guide#Configuration configure] the third gHN to join it to the infrastructure scope and
−
##* [[VRE_Management_Installation#Software_Repository|deploy and populate a Software Repository]] there
+
##* deploy a [[VRE_Management_Installation#Software_Gateway|Software Gateway]] instance and configure it to join both the infrastructure and the VO scope
−
##* [[VRE_Management_Installation#VREManager|deploy a VREManager Service]] there
+
##* 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
 
##start the 3 containers following the order of the deployments and verify that they work properly
−
#setup the VO
 
−
##identify 3 machines to dedicate to the VO Enabling Services
 
−
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Installation install gCore] in the 3 machines 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] one gHN as root, join it to the VO as startScope and [[Information_System_Installation|install the IS core services]] (IS-IC, IS-Registry, IS-Notifier) there dedicated to the VO (named ''IS VO gHN'')
 
−
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] one gHN (named ''VREManager VO gHN'') to join it to the VO as start scope and [[Core_Services_Installation#DL_Management|install and configure a DL Management Service]] there
 
  
−
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] the gHN to join to the VO scope and
+
=== Other possible configurations ===
−
##* deploy the [[Information_System_Installation#Version_2.0.0_or_higher|IS-Collector]] on the node
+
−
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] the second gHN as ROOT and to join to the VO scope and
+
−
##* deploy the [[Information_System_Installation#IS-Registry|IS-Registry]] on the node
+
−
##* deploy the [[Information_System_Installation#IS-Notifier|IS-Notifier]] on the node
+
−
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] one third gHN to join it to the VO scope and
+
−
##* [[VRE_Management_Installation#VREModeler|deploy and configure a VREModeler]] to join the VO scope
+
−
##* [[VRE_Management_Installation#VREManager|deploy and configure VREManager Service]] to join the VO scope
+
−
##start the 3 containers following the order of the deployments and verify that they work properly
+
−
 
+
−
+
−
##start the container on the ''IS VO gHN'' and then on the ''VREManager VO gHN'' and verify that they work properly
+
−
#configure and start generic gHNs
+
−
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Installation install gCore] in each machine and copy the VO Map files under the ''$GLOBUS_LOCATION/config'' folder
+
−
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] the gHNs to join the VO as start scope:
+
−
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Verify_the_Installation start the container] on each machine and verify that the gHN is correctly published both in the root VO and in the VO IS
+
−
#setup the portal by following the ... instructions.
+
−
#configure one or more VREs by exploiting the [[Administration]] user interface capability.
+
−
 
+
−
==== Other possible configurations ====
+
 
Alternative configurations can improve the infrastructure performances. In particular:
 
Alternative configurations can improve the infrastructure performances. In particular:
−
* the IS-Notifier can be hosted on a different (and standard, i.e. non-root) gHN with respect to the other two IS core services
+
* the IS-Notifier can be hosted on a different gHN with respect to the IS-Registry service
−
* the Software Repository can be hosted on a different (and standard, i.e. non-root) gHN with respect to the VREManager service
+
* the Software Gateway can be hosted on a different gHN with respect to the Resource Management services
−
* multiple VOs can be defined  
+
* multiple Virtual Organizations can be defined and deployed
−
* more than one IS can be setup for each VO in order to distribute the load over them
+
  
−
The 'optimal' configuration mainly depends on the number of available gHNs. More gHNs joining the infrastructure means a better distribution of resources and services across them.
+
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"