Difference between revisions of "VO installation"
From Gcube Wiki
Manuele.simi (Talk | contribs) |
Manuele.simi (Talk | contribs) |
||
Line 1: | Line 1: | ||
These are the steps needed to setup a new VO | These are the steps needed to setup a new VO | ||
− | # | + | #decide the [https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Scope_Management#Modelling_Scope scope] hierarchy, i.e. the name of the VO and the gCube infrastructure to join |
+ | #identify a set of machines to turn on as gHNs (their number may vary depending on the VO needs) | ||
+ | #[[Information_System_Installation#Service_Map|prepare a Service Map]] file for the VO scope | ||
#install the VO enabling services: | #install the VO enabling services: | ||
##identify 3 machines to dedicate to the VO Enabling Services | ##identify 3 machines to dedicate to the VO Enabling Services |
Revision as of 16:42, 5 October 2009
These are the steps needed to setup a new VO
- decide the scope hierarchy, i.e. the name of the VO and the gCube infrastructure to join
- identify a set of machines to turn on as gHNs (their number may vary depending on the VO needs)
- 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
- start the 3 containers following the order of the deployments and verify that they work properly
- create the related group in VOMS