Difference between revisions of "VO configuration"

From Gcube Wiki
Jump to: navigation, search
m
 
(20 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
[[Category:Administrator's Guide]]
 
The configuration of a new Virtual Organization requires the following steps:
 
The configuration of a new Virtual Organization requires the following steps:
  
−
# configure the gHNs hosting the [[VO_installation|Enabling Services]];
 
−
# configure the [[VO_installation|Enabling Services]];
 
−
# create a new group in VOMS from the [http://voms.research-infrastructures.eu/ VOMS-Admin interface] with the same name of the VO as sub-group of the (e.g. if the VO scope is ''/d4science/FARM'', the new group ''FARM'' must be created within the group ''d4science'');
 
 
# assign to at least one authorized user the right of ''VO-Admin'';
 
# assign to at least one authorized user the right of ''VO-Admin'';
−
# create and register in the IS a ''PortletLayoutResource''. This generic resource describes the portlets associated to the VO and defines which roles can access them. The name of the resource must be ''Layout_<VOScope>'';
+
# configure a [[Monitoring_System|Monitoring]] instance by providing the [[Information_System_Installation#Service_Map|Service Map]] for the VO scope;
−
# configure a [http://monitor.d4science.research-infrastructures.eu/iv/ Monitoring] instance by providing the [[Information_System_Installation#Service_Map|Service Map]] for the VO scope
+
# [https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] the gHN running on the Portal to join the new VO Scope;
−
# [https://wiki.gcore.research-infrastructures.eu/gCube/index.php/Administrator_Guide#Configuration configure] the gHN running on the Portal to join the new VO Scope
+
# [[Managing_the_VO#Editing_the_VO_Information_Space|create and register]] in the IS a [[ScenarioCollectionInfo|''ScenarioCollectionInfo'']] resource for the VO;
 
# populate the Software Repository instance belonging the VO Scope. One of the following must be performed:
 
# populate the Software Repository instance belonging the VO Scope. One of the following must be performed:
−
#* if a dedicated instance has been deployed (step .4.5 of [[VO_installation|VO installation]] procedure has been performed), the instance must be populated with the Software Archives
+
#* if a dedicated instance has been deployed (step .4.5 of [[VO_installation|VO installation]] procedure has been performed), the instance must be populated with the Software Archives by using the [[Software_Repository#Test-Suite|SR test suite]]
 
#* if there is no dedicated instance in the VO, the instance of the above Scope (i.e. the Infrastructure Scope) must be reconfigure to join the new VO Scope and then repopulated with the Software Archives
 
#* if there is no dedicated instance in the VO, the instance of the above Scope (i.e. the Infrastructure Scope) must be reconfigure to join the new VO Scope and then repopulated with the Software Archives

Latest revision as of 10:09, 24 July 2013

The configuration of a new Virtual Organization requires the following steps:

  1. assign to at least one authorized user the right of VO-Admin;
  2. configure a Monitoring instance by providing the Service Map for the VO scope;
  3. configure the gHN running on the Portal to join the new VO Scope;
  4. create and register in the IS a ScenarioCollectionInfo resource for the VO;
  5. populate the Software Repository instance belonging the VO Scope. One of the following must be performed:
    • if a dedicated instance has been deployed (step .4.5 of VO installation procedure has been performed), the instance must be populated with the Software Archives by using the SR test suite
    • if there is no dedicated instance in the VO, the instance of the above Scope (i.e. the Infrastructure Scope) must be reconfigure to join the new VO Scope and then repopulated with the Software Archives
Retrieved from "https://gcube.wiki.gcube-system.org/index.php?title=VO_configuration&oldid=19363"