Difference between revisions of "VO installation"

From Gcube Wiki
Jump to: navigation, search
Line 1: Line 1:
In order to setup the VO:
+
These are the steps needed to setup a new VO
 +
 
 +
#prepare the Service Map
 +
 
 +
#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
 
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Installation install gCore] in the 3 machines and copy the 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 Service Map files under the ''$GLOBUS_LOCATION/config' folder
Line 11: Line 15:
 
##* deploy a [[VRE_Management_Installation#VREManager|VREManager]] instance and configure it to join the VO scope
 
##* deploy a [[VRE_Management_Installation#VREManager|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
 
##start the 3 containers following the order of the deployments and verify that they work properly
 +
 +
#create the related group in VOMS

Revision as of 16:30, 5 October 2009

These are the steps needed to setup a new VO

  1. prepare the Service Map
  1. install the VO enabling services:
    1. identify 3 machines to dedicate to the VO Enabling Services
    2. install gCore in the 3 machines and copy the Service Map files under the $GLOBUS_LOCATION/config' folder
    3. configure the first gHN to join to the VO scope and
      • deploy the IS-Collector and configure it to join the VO scope
    4. 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
    5. 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
    6. start the 3 containers following the order of the deployments and verify that they work properly
  1. create the related group in VOMS