Difference between revisions of "VO configuration"
From Gcube Wiki
Manuele.simi (Talk | contribs) |
m |
||
| (18 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: | ||
| − | |||
| − | |||
| − | |||
# assign to at least one authorized user the right of ''VO-Admin''; | # assign to at least one authorized user the right of ''VO-Admin''; | ||
| − | # [[ | + | # configure a [[Monitoring_System|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 09:09, 24 July 2013
The configuration of a new Virtual Organization requires the following steps:
- assign to at least one authorized user the right of VO-Admin;
- configure a 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 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 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
