Difference between revisions of "VO installation"

From Gcube Wiki
Jump to: navigation, search
 
(15 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
[[Category:Administrator's Guide]]
 
These are the steps needed to setup a new Virtual Organization:
 
These are the steps needed to setup a new Virtual Organization:
 
+
#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 and 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  
#identify a set of machines to turn on as gHNs (their number may vary depending on the VO needs)
+
#identify at least 8 machines to turn on as gHNs (however, 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 14: Line 14:
 
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] the third gHN to join it to the VO scope and
 
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] the third gHN to join it to the VO scope and
 
##* 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#Resource_Manager|Resource Manager]] instance and a [[VRE_Management_Installation#Resource_Broker|Resource Broker]] instance and configure them to join the VO scope
 +
##* deploy a [[VRE_Management_Installation#Software_Gateway|Software Gateway]] 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
#create the related group in VOMS
 
#configure and start a few generic gHNs to use for future dynamic deployment activities (e.g., deployment of VO level services and VRE creation)
 
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Installation install gCore] in each machine 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 gHNs to join the VO scope
 
##[https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Verify_the_Installation start the container] on each machine and verify that the gHN is correctly published both in the infrastructure and in the VO Information Systems.
 

Latest revision as of 15:23, 20 November 2014

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 8 machines to turn on as gHNs (however, 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 Resource Manager instance and a Resource Broker instance and configure them to join the VO scope
      • deploy a Software Gateway 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
    5. start the 3 containers following the order of the deployments and verify that they work properly