Difference between revisions of "VO configuration"
From Gcube Wiki
Manuele.simi (Talk | contribs) |
Manuele.simi (Talk | contribs) |
||
| Line 8: | Line 8: | ||
# [[Managing_the_VO#Editing_the_VO_Information_Space|create and register]] in the IS a [[ScenarioCollectionInfo|''ScenarioCollectionInfo'']] resource for the VO. | # [[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 by using the [https://technical.wiki.d4science.research-infrastructures.eu/documentation/index.php/Software_Repository#Test-Suite|SR Client] | + | #* 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 [https://technical.wiki.d4science.research-infrastructures.eu/documentation/index.php/Software_Repository#Test-Suite | SR Client] |
#* 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 | ||
Revision as of 18:42, 17 December 2009
The configuration of a new Virtual Organization requires the following steps:
- create a new group in VOMS from the VOMS-Admin interface with the same name of the VO as sub-group of the (e.g. if the VO scope is /d4science.research-infrastructures.eu/FARM, the new group FARM must be created within the group d4science.research-infrastructures.eu);
- assign to at least one authorized user the right of VO-Admin;
- configure a [Monitoring_System Monitoring] instance by providing the Service Map for the VO scope
- configure the gHN running on the Portal to join the new VO Scope
- create and register in the IS the PortletLayoutResource resource for the VO. 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_<VOName>, e.g. Layout_d4science.research-infrastructures.eu_FARM;
- create and register in the IS a ScenarioCollectionInfo resource for the VO.
- 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 Client
- 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
