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 27: | Line 27: | ||
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] the third gHN to join it to the infrastructure scope and | ##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] the third gHN to join it to the infrastructure scope and | ||
##* deploy a [[VRE_Management_Installation#Software_Repository|Software Repository]] instance and configure it to join both the infrastructure and the VO scope | ##* deploy a [[VRE_Management_Installation#Software_Repository|Software Repository]] instance and configure it to join both the infrastructure and the VO scope | ||
| − | ##* deploy a [[VRE_Management_Installation# | + | ##* 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 | ||
#create the related group in VOMS | #create the related group in VOMS | ||
Revision as of 23:47, 2 June 2010
| 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 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 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
- 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.
