Difference between revisions of "Verifying the Virtual Organization correctness"
From Gcube Wiki
Manuele.simi (Talk | contribs) |
Manuele.simi (Talk | contribs) |
||
Line 5: | Line 5: | ||
#* by selecting the entry and then the gHN Resource Type, all the gHNs joined to the VO must be in the [https://service.wiki.d4science-ii.research-infrastructures.eu/service/index.php/Procedure_Infrastructure_Certification ''Certified''] status | #* by selecting the entry and then the gHN Resource Type, all the gHNs joined to the VO must be in the [https://service.wiki.d4science-ii.research-infrastructures.eu/service/index.php/Procedure_Infrastructure_Certification ''Certified''] status | ||
#* by selecting the entry and then the Running Instance Resource Type, all the instances belonging the VO must be in the ''Ready'' status | #* by selecting the entry and then the Running Instance Resource Type, all the instances belonging the VO must be in the ''Ready'' status | ||
− | |||
# in the Portal, after the log on as authorized user: | # in the Portal, after the log on as authorized user: | ||
#* a new entry in the menu (below the label ''Available VO/VRE to load'') with the VO Scope name is available | #* a new entry in the menu (below the label ''Available VO/VRE to load'') with the VO Scope name is available |
Revision as of 00:55, 3 December 2009
If a VO is properly installed and configured, all the following conditions must be verified:
- in the IS Monitoring:
- a new entry in the top-left menu with the VO Scope name is available
- by selecting the entry and then the gHN Resource Type, all the gHNs joined to the VO must be in the Certified status
- by selecting the entry and then the Running Instance Resource Type, all the instances belonging the VO must be in the Ready status
- in the Portal, after the log on as authorized user:
- a new entry in the menu (below the label Available VO/VRE to load) with the VO Scope name is available
- by selecting the entry and then pressing the Enter button, it is possible to log on in the VO
- once inside the VO, all the administration (such as VO Management) tabs are visible
- by clicking on any tabs, the related features are correctly displayed and can be exploited without any error/warning message