Difference between revisions of "VO installation"
From Gcube Wiki
Manuele.simi (Talk | contribs) m (VO enabling installation moved to VO installation) |
Manuele.simi (Talk | contribs) |
||
| Line 2: | Line 2: | ||
#prepare the Service Map | #prepare the Service Map | ||
| − | |||
#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 | ||
| Line 15: | Line 14: | ||
##* 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 | #create the related group in VOMS | ||
Revision as of 16:33, 5 October 2009
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
- 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
