Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "NGI DE:GOP/resource centre certification for UNICORE"

From EGIWiki
Jump to navigation Jump to search
Line 2: Line 2:


Requirements from EGI (https://documents.egi.eu/public/RetrieveFile?docid=31&version=7&filename=EGI-RC-OLA-2011-v1.1final.pdf)
Requirements from EGI (https://documents.egi.eu/public/RetrieveFile?docid=31&version=7&filename=EGI-RC-OLA-2011-v1.1final.pdf)
* register with GOCDB according to EGI-RC-OLA
* run site-BDII and publish data to central BDII  (UNICORE will allow for that with its next release in Feb/March 2013)
* run site-BDII and publish data to central BDII  (UNICORE will allow for that with its next release in Feb/March 2013)
* support a way to enable service monitoring and security monitoring. As UNICORE's UVOS has a different interface compared to VOMS, enabling the OPS VO is not possible. Instead add to your XUUDB, to the authorization file, or to UVOS the robot certificate NGI-DE (at KIT) is using for monitoring.  
* support a way to enable service monitoring and security monitoring. As UNICORE's UVOS has a different interface compared to VOMS, enabling the OPS VO is not possible. Instead add to your XUUDB, to the authorization file, or to UVOS the robot certificate NGI-DE (at KIT) is using for monitoring.  
* for testing and toubleshooting additional robot or user certificates (from VO dteam) might havew to be added.
* for testing and toubleshooting additional robot or user certificates (from VO dteam) might havew to be added.
* support one non-monitoring/troubleshooting user group, which is registered in EGI's Operations Portal4. As VO support in UNICORE is different from the one in gLite, this cannot be done currently. UVOS needs to be accepted by EGI Operations first....
* support one non-monitoring/troubleshooting user group, which is registered in EGI's Operations Portal4. As VO support in UNICORE is different from the one in gLite, this cannot be done currently. UVOS needs to be accepted by EGI Operations first....
* make sure your centre is up and running more than 70% per month and its reliability is more than 75%

Revision as of 16:54, 12 November 2012

--- How to certify a resource centre with UNICORE services only: ---

Requirements from EGI (https://documents.egi.eu/public/RetrieveFile?docid=31&version=7&filename=EGI-RC-OLA-2011-v1.1final.pdf)

  • register with GOCDB according to EGI-RC-OLA
  • run site-BDII and publish data to central BDII (UNICORE will allow for that with its next release in Feb/March 2013)
  • support a way to enable service monitoring and security monitoring. As UNICORE's UVOS has a different interface compared to VOMS, enabling the OPS VO is not possible. Instead add to your XUUDB, to the authorization file, or to UVOS the robot certificate NGI-DE (at KIT) is using for monitoring.
  • for testing and toubleshooting additional robot or user certificates (from VO dteam) might havew to be added.
  • support one non-monitoring/troubleshooting user group, which is registered in EGI's Operations Portal4. As VO support in UNICORE is different from the one in gLite, this cannot be done currently. UVOS needs to be accepted by EGI Operations first....
  • make sure your centre is up and running more than 70% per month and its reliability is more than 75%