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 "Verify Configuration Records"
Jump to navigation
Jump to search
| Line 34: | Line 34: | ||
|CERN | |CERN | ||
|https://ggus.eu/index.php?mode=ticket_info&ticket_id=127592 | |https://ggus.eu/index.php?mode=ticket_info&ticket_id=127592 | ||
| | |SOLVED | ||
|- | |- | ||
|NGI_AEGIS | |NGI_AEGIS | ||
Revision as of 15:32, 25 April 2017
2017-04-07
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: