Difference between revisions of "Verify Configuration Records"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
'''2017-07-04''' | '''2017-07-04''' | ||
Line 7: | Line 6: | ||
# NGI managers should review the people registered and the roles assigned to them, and in particular check the following information: | # NGI managers should review the people registered and the roles assigned to them, and in particular check the following information: | ||
#* E-Mail | #* E-Mail | ||
#* ROD E-Mail | |||
#* Security E-Mail | |||
NGI Managers should also review the status of the "not certified" RCs, in according to the RC Status Workflow: https://wiki.egi.eu/wiki/PROC09#Resource_Center_status_Workflow | NGI Managers should also review the status of the "not certified" RCs, in according to the RC Status Workflow: https://wiki.egi.eu/wiki/PROC09#Resource_Center_status_Workflow | ||
# RCs administrators should review the people registered and the roles assigned to them, and in particular check the following information: | |||
- E-Mail | - E-Mail | ||
- telephone numbers | - telephone numbers |
Revision as of 09:52, 10 April 2017
2017-07-04
On a yearly basis, the information registered into GOC-DB need to be verified. NGIs and RCs have been asked to check them. In particular:
- NGI managers should review the people registered and the roles assigned to them, and in particular check the following information:
- ROD E-Mail
- Security E-Mail
NGI Managers should also review the status of the "not certified" RCs, in according to the RC Status Workflow: https://wiki.egi.eu/wiki/PROC09#Resource_Center_status_Workflow
- RCs administrators should review the people registered and the roles assigned to them, and in particular check the following information:
- E-Mail - telephone numbers - CSIRT E-Mail
RC administrators should also review the information related to the registered service endpoints.
Please try to complete the review by Apr 28th. Keep us updated during the process and don't hesitate to ask any question.
Thanks for your collaboration, EGI Operations