Difference between revisions of "Verify Configuration Records"
Jump to navigation
Jump to search
Line 99: | Line 99: | ||
|NGI_IL | |NGI_IL | ||
| https://ggus.eu/index.php?mode=ticket_info&ticket_id=147053 | | https://ggus.eu/index.php?mode=ticket_info&ticket_id=147053 | ||
| | | SOLVED | ||
|- | |- | ||
|NGI_IT | |NGI_IT |
Revision as of 11:25, 20 May 2020
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 |
2020-05-20
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 22nd.
To track the process, the following tickets have been opened: