Difference between revisions of "Verify Configuration Records"
Jump to navigation
Jump to search
Line 8: | Line 8: | ||
#* ROD E-Mail | #* ROD E-Mail | ||
#* Security E-Mail | #* Security E-Mail | ||
#:NGI Managers should also review the status of the "not certified" RCs, in according to the | #:NGI Managers should also review the status of the "not certified" RCs, in according to the [https://wiki.egi.eu/wiki/PROC09#Resource_Center_status_Workflow RC Status Workflow]; | ||
# '''RCs administrators should review the people registered and the roles assigned to them, and in particular check the following information:''' | # '''RCs administrators should review the people registered and the roles assigned to them, and in particular check the following information:''' | ||
#* E-Mail | #* E-Mail |
Revision as of 10:17, 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;
- RCs administrators should review the people registered and the roles assigned to them, and in particular check the following information:
- telephone numbers
- CSIRT E-Mail
- RC administrators should also review the information related to the registered service endpoints.
The process should be completed by Apr 28th.
To track the process, the following tickets have been opened: