Difference between revisions of "Administrator's Guide: How to set up a gCube infrastructure"
From Gcube Wiki
Manuele.simi (Talk | contribs) (→Minimal deployment scenario) |
(→Other possible configurations) |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Category:Administrator's Guide]] | ||
__NOTOC__ | __NOTOC__ | ||
{| align="right" style="color:red; border:1px solid #aaa; background-color: #f9f9f9; padding: 5px; font-size: 95%;" cellspacing="0" | {| align="right" style="color:red; border:1px solid #aaa; background-color: #f9f9f9; padding: 5px; font-size: 95%;" cellspacing="0" | ||
| Line 14: | Line 15: | ||
In this section, we report the steps to setup a gCube infrastructure: | In this section, we report the steps to setup a gCube infrastructure: | ||
| − | #decide the [https:// | + | #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 the infrastructure | #[[Information_System_Installation#Service_Map|prepare a Service Map]] file for the infrastructure | ||
#install the infrastructure enabling services: | #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:// | + | ##[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:// | + | ##[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 | ##* 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:// | + | ##[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-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 | ##* deploy and configure an [[Information_System_Installation#IS-Notifier|IS-Notifier]] instance and configure it to join the infrastructure scope | ||
| − | ##[https:// | + | ##[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# | + | ##* 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 | ##* 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 | ||
| − | |||
=== Other possible configurations === | === 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 gHN with respect to the IS-Registry service | * the IS-Notifier can be hosted on a different gHN with respect to the IS-Registry service | ||
| − | * the Software | + | * 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 | * 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 '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
| 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:
- decide the 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)
- prepare a Service Map file for the infrastructure
- install the infrastructure enabling services:
- identify 3 machines to dedicate to the Infrastructure Enabling Services
- install gCore in the 3 machines and copy the two Service Map files under the $GLOBUS_LOCATION/config folder
- 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
- 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
- configure the third gHN to join it to the infrastructure scope and
- deploy a Software Gateway instance and configure it to join both the infrastructure and the VO scope
- deploy a Resource Manager instance and a 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.
