Difference between revisions of "Administrator's Guide: How to set up a gCube infrastructure"
From Gcube Wiki
Manuele.simi (Talk | contribs) |
Manuele.simi (Talk | contribs) (→Minimal deployment scenario) |
||
| Line 4: | Line 4: | ||
=== Minimal deployment scenario === | === Minimal deployment scenario === | ||
| − | 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://wiki.gcore.research-infrastructures.eu/gCube/index.php/Scope_Management#Modelling_Scope scope] | + | #decide the [https://wiki.gcore.research-infrastructures.eu/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 | + | #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 | + | #[[Information_System_Installation#Service_Map|prepare a Service Map]] file for 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://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 | ||
| Line 21: | Line 21: | ||
##* deploy a [[VRE_Management_Installation#VREManager|VREManager]] instance and configure it to join the infrastructure scope | ##* deploy a [[VRE_Management_Installation#VREManager|VREManager]] instance and configure it 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 | ||
| − | # | + | #create the related group in VOMS |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
=== Other possible configurations === | === Other possible configurations === | ||
Revision as of 17:46, 5 October 2009
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 a 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 a IS-Registry instance and configure it to join the infrastructure scope
- deploy and configure a 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 Repository instance and configure it to join both the infrastructure and the VO scope
- deploy a VREManager instance and configure it to join the infrastructure scope
- start the 3 containers following the order of the deployments and verify that they work properly
- create the related group in VOMS
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 Repository can be hosted on a different gHN with respect to the VREManager service
- 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. More gHNs joining the infrastructure means a better distribution of resources and services across them.
