Difference between revisions of "EGI Infrastructure operations oversight"
Line 1: | Line 1: | ||
{{Template:Op menubar}} __NOTOC__ | {{Template:Op menubar}} __NOTOC__ | ||
[[Category:Grid Oversight]] | |||
'''<br>''' | '''<br>''' | ||
Line 41: | Line 42: | ||
|} | |} | ||
Revision as of 14:41, 12 October 2012
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Grid operations oversight activitie over the NGI infrastructures is needed for detecting problems, coordinating the diagnosis, and monitoring the problems during the entire lifecycle until resolution. Oversight of the NGI Grid is based on monitoring of status of services operated by sites, opening of tickets and their follow up for problem resolution. EGI.org supports and actively controls the overall status of Grid services and sites, opening of tickets for requesting problem fixing, and tackling of residual problems not successfully distributed to NGI’s.
Grid operations oversight activities are performed by COD team on the EGI level and by ROD teams on the Operations Centres level.
COD is a small team responsible for coordination of RODs, provided on a global layer. COD represents the whole ROD structure in terms of technical requirements for operations tools as well as on political level.
ROD is a team responsible for solving problems on the infrastructure within NGI according to agreed procedures. They ensure that problems are properly recorded and progress according to specified time lines. They ensure that necessary information is available to all parties. The team is provided by each NGI and requires procedural knowledge on the process (rather than technical skills) for their work.
People and contactPeople performing the activities and contact points to them can be found:
DutiesCOD team is responsible for the global oversight over the whole EGI infrastructure. More details: COD_Duties ROD team is responsible for handling of operational problems within own NGI. More details: ROD_duties |
Resources
|