Difference between revisions of "Verify Configuration Records"
Jump to navigation
Jump to search
Line 79: | Line 79: | ||
|NGI_FRANCE | |NGI_FRANCE | ||
|https://ggus.eu/index.php?mode=ticket_info&ticket_id=135020 | |https://ggus.eu/index.php?mode=ticket_info&ticket_id=135020 | ||
| | |in progress | ||
|- | |- | ||
|NGI_GE | |NGI_GE |
Revision as of 09:28, 6 June 2018
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Documentation menu: | Home • | Manuals • | Procedures • | Training • | Other • | Contact ► | For: | VO managers • | Administrators |
2018-05-09
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 June 6th.
To track the process, the following tickets have been opened: