Difference between revisions of "VO installation"
From Gcube Wiki
Manuele.simi (Talk | contribs) |
Manuele.simi (Talk | contribs) |
||
Line 4: | Line 4: | ||
#select the [[Administrator's_Guide:How_to_set_up_a_gCube_infrastructure|gCube infrastructure]] to join | #select the [[Administrator's_Guide:How_to_set_up_a_gCube_infrastructure|gCube infrastructure]] to join | ||
#decide the [https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Scope_Management#Modelling_Scope scope] hierarchy, i.e. the name of the VO within the new infrastructure | #decide the [https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Scope_Management#Modelling_Scope scope] hierarchy, i.e. the name of the VO within the new infrastructure | ||
− | #identify at least 6 machines to turn on as gHNs (their number may vary depending on the VO needs) | + | #identify at least 6 machines to turn on as gHNs (their number may vary depending on the VO needs). These machine will serve the needs for a typical exploitation scenario of the VO: |
+ | :* 3 machines for the enabling services | ||
+ | :* 3 machines for the VO services (Content Management, Indexes and Metadata Management) | ||
+ | : plus, 2 machines for each VRE that is expected to be deployed within the VO | ||
#[[Information_System_Installation#Service_Map|prepare a Service Map]] file for the VO scope | #[[Information_System_Installation#Service_Map|prepare a Service Map]] file for the VO scope | ||
#install the VO enabling services: | #install the VO enabling services: |
Revision as of 18:12, 17 December 2009
These are the steps needed to setup a new Virtual Organization:
- select the gCube infrastructure to join
- decide the scope hierarchy, i.e. the name of the VO within the new infrastructure
- identify at least 6 machines to turn on as gHNs (their number may vary depending on the VO needs). These machine will serve the needs for a typical exploitation scenario of the VO:
- 3 machines for the enabling services
- 3 machines for the VO services (Content Management, Indexes and Metadata Management)
- plus, 2 machines for each VRE that is expected to be deployed within the VO
- prepare a Service Map file for the VO scope
- install the VO enabling services:
- identify 3 machines to dedicate to the VO Enabling Services
- install gCore in the 3 machines and copy the Service Map files under the $GLOBUS_LOCATION/config folder
- configure the first gHN to join to the VO scope and
- deploy the IS-Collector and configure it to join the VO scope
- configure the second gHN as ROOT and to join to the VO scope and
- deploy a IS-Registry instance and configure it to join the VO scope
- deploy a IS-Notifier instance and configure it to join the VO scope
- configure the third gHN to join it to the VO scope and
- deploy a VREModeler instance and configure it to join the VO scope
- deploy a VREManager instance and configure it to join the VO scope
- (optional) deploy a Software Repository instance and configure it to join the VO scope
- start the 3 containers following the order of the deployments and verify that they work properly
- configure and start a few generic gHNs to use for future dynamic deployment activities (e.g., deployment of VO level services and VRE creation)
- install gCore in each machine and copy the Service Map files under the $GLOBUS_LOCATION/config folder
- configure the gHNs to join the VO scope
- start the container on each machine and verify that the gHN is correctly published both in the infrastructure and in the VO Information Systems.