Difference between revisions of "VO installation"

From Gcube Wiki
Jump to: navigation, search
Line 6: Line 6:
 
#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: ''(i)'' 3 machines for the enabling services, ''(ii)'' 3 machines for the VO services (Content Management, Indexes and Metadata Management), and ''(iii)'' then consider, 2 machines for each VRE that is expected to be deployed within the VO
 
#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: ''(i)'' 3 machines for the enabling services, ''(ii)'' 3 machines for the VO services (Content Management, Indexes and Metadata Management), and ''(iii)'' then consider, 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:
##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 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
+
 
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] the first gHN to join to the VO scope and  
 
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] the first gHN to join to the VO scope and  
 
##* deploy the [[Information_System_Installation#Version_2.0.0_or_higher|IS-Collector]] and configure it to join the VO scope
 
##* deploy the [[Information_System_Installation#Version_2.0.0_or_higher|IS-Collector]] and configure it to join the VO scope
Line 17: Line 16:
 
##* deploy a [[VRE_Management_Installation#VREModeler|VREModeler]] instance and configure it to join the VO scope
 
##* deploy a [[VRE_Management_Installation#VREModeler|VREModeler]] 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
 
##* deploy a [[VRE_Management_Installation#VREManager|VREManager]] instance and configure it to join the VO scope
##* deploy a [[VRE_Management_Installation#Software_Repository|Software Repository]] instance and configure it to join the VO scope; this is an optional step, since also the Software Repository can be joined to the new VO via the Resource Management tool
+
##* deploy a [[VRE_Management_Installation#Software_Repository|Software Repository]] instance and configure it to join the VO scope; this is an optional step, since also the infrastructure level Software Repository can be joined to the new VO via the Resource Management tool
 +
 
 +
 
 
##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

Revision as of 21:21, 17 December 2009

These are the steps needed to setup a new Virtual Organization:


  1. select the gCube infrastructure to join
  2. decide the scope hierarchy, i.e. the name of the VO within the new infrastructure
  3. 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: (i) 3 machines for the enabling services, (ii) 3 machines for the VO services (Content Management, Indexes and Metadata Management), and (iii) then consider, 2 machines for each VRE that is expected to be deployed within the VO
  4. prepare a Service Map file for the VO scope
  5. install the VO Enabling Services:
    1. install gCore in 3 machines and copy the Service Map files under the $GLOBUS_LOCATION/config folder
    2. configure the first gHN to join to the VO scope and
      • deploy the IS-Collector and configure it to join the VO scope
    3. 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
    4. 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
      • deploy a Software Repository instance and configure it to join the VO scope; this is an optional step, since also the infrastructure level Software Repository can be joined to the new VO via the Resource Management tool


    1. start the 3 containers following the order of the deployments and verify that they work properly