Alert.png 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 "EGI Infrastructure operations oversight"

From EGIWiki
Jump to navigation Jump to search
Line 19: Line 19:


'''EGI Operations support '''team is a small team responsible to provide  
'''EGI Operations support '''team is a small team responsible to provide  
# Coordination of activities with the EGI.eu operations team, the Operations Management Board and the User Community Board.
# Central Technical Support to site administrators, NGI operators, EGI.eu operations staff and new user communities. This includes  
# Central Technical Support to site administrators, NGI operators, EGI.eu operations staff and new user communities. This includes  
#* technical support to the EGI.eu operations activities  
#* technical support to the EGI.eu operations activities  

Revision as of 14:45, 19 August 2014

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


EGI Infrastructure Operations Oversight menu: Home EGI.eu Operations Team Regional Operators (ROD) 




EGI Infrastructure operations oversight activity is provided by:

  • EGI.eu Operations team
  • EGI Operations Support
  • Regional Operators on Duty (ROD) teams

Oversight activity 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 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 services and sites, opening of tickets for requesting problem fixing, and tackling of residual problems not successfully distributed to NGI’s.


EGI.eu Operations team is a small team responsible for


EGI Operations support team is a small team responsible to provide

  1. Coordination of activities with the EGI.eu operations team, the Operations Management Board and the User Community Board.
  2. Central Technical Support to site administrators, NGI operators, EGI.eu operations staff and new user communities. This includes
    • technical support to the EGI.eu operations activities
    • technical support to ROD teams through target training activities
    • coordination of technical working groups
    • technical support to new resource centres in their certification phase when requested by the Operations Centre because of lack of sufficient local expertise
    • certification and technical support for new infrastructures being integrated by providing assistance and training about EGI operations services, policies and procedures, and developing documentation as needed
  3. Resource Allocation
    • defining service management processes for resource allocation and other EGI.eu operations services
    • training, communicating, adapting, enforcing these at an NGI level
    • defining requirements for the operations tools that generate from the provisioning of these new services
    • managing resource allocation process (eg. operating e-grant tool)


Regional Operators on Duty (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. Depending on how an NGI is organized there might be a number of members in the ROD team who work on duty roster (shifts on a daily or weekly basis), or there may be one person working as ROD on a daily basis and a few deputies who take over the responsibilities when necessary. This latter model is generally more suitable for small NGIs.